Docker Host Ip Install Docker Itself

But with the introduction of Docker, and the SQL Server support for it, its now real.

How can I be that stupid to work on MacOS when Im dependent on SQL Server In my case it wasnt 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.

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.

Because now I can run SQL Server 2017 directly on my Mac and I even dont really need a Windows VM anymore.

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.

Docker Host Ip Install Docker Itself

I dont want to go into the details how to install Docker itself, because the necessary steps are very well documented.

In my case I have decided to try out the latest CTP version of SQL Server 2019.

And that creates the actual Docker Container, which is finally the exectuable that you are executing.

In our case we have to accept the EULA to be able to use SQL Server.

In my case I bind the default SQL Server port of 1433 within the Container to the port 1433 on my Mac.

If you have multiple SQL Server Containers, you can also bind them to different ports on your host machine to access them independently from each other.

This just means that you can close your Terminal, and your Docker Container is still running in the background.

But how do we access SQL Server Of course, I can start up a Windows VM, and use SQL Server Management Studio to access SQL Server.

But then Im again dependent on a Windows VM, which also needs periodically updates, and it would be also a huge overhead to deploy a whole Windows VM just for SQL Server Management Studio.

Dont get me wrong: compared to SQL Server Management Studio, Azure Data Studio is nice but.

What do I need more For the kind of work that Im doing, its enough.

There are our system databases, the crazy default settings, and thats it.

So you have to create your own databases, or you take an existing database (maybe from a Windows-based SQL Server installation) and you restore it in your Docker Container.

First of all you have to copy your backup file into the Docker Container.

But you cant do a regular cp command from the Terminal, because that command has no idea about your Docker Container.

But the destination folders are different as on a Windows-based SQL Server installation, therefore we also have to move our data and log files.

Therefore I have executed in the first step the following command to get the logical file names of our database backup.

And now we have our AdventureWorks database restored in our Docker Container.

Docker For Mac Host Ip