And that creates the actual Docker Container, which is finally the exectuable that you are executing. In Docker you can “install” an image by running it. Therefore we also have to “install” the pulled Docker Image.
CONNECT SQL SERVER ON MAC INSTALL
You can think about a Docker Image like an ISO file: it’s just an image, and you can’t run it directly, because you have to install it. When you have pulled the image, you can see it with the docker images command in your Terminal: In my case I have decided to try out the latest CTP version of SQL Server 2019:ĭocker pull /mssql/server:2019-CTP2.1-ubuntu
CONNECT SQL SERVER ON MAC HOW TO
I don’t want to go into the details how to install Docker itself, because the necessary steps are very well documented.īefore you can create a Docker Container for SQL Server, you have to pull the correct Docker Image from the Docker Registry. Installing SQL Server in a Docker Containerīefore you can install SQL Server in a Docker Container on the Mac, you have to install and configure of course Docker itself. In this blog posting I want to show you how you can do the same and run SQL Server directly on your Mac in a Docker container. Because now I can run SQL Server 2017+ directly on my Mac and I even don’t really need a Windows VM anymore.
Therefore running natively on MacOS was not a big deal for me, and for the last resort I always have a Windows VM which runs in VMware Fusion on my Mac.īut since the introduction of the Container concept through Docker and the possibility to run SQL Server directly in a Container, my life was changing even better. How can I be that stupid to work on MacOS when I’m dependent on SQL Server? In my case it wasn’t that terrible, because my main work is about content creation (writing blog postings, articles, presentations, training videos) and very often I was only connecting through a RDP connection to a remote SQL Server. Years ago when I switched from Windows to Mac, people have told me regularily that I’m crazy.
0 kommentar(er)
