Skip to main content

An Introduction to Conatiners and Docker: Switch to Windows Containers

This is Chris Gibson's second post. This post follows on from his first post called: An Introduction to Containers and Docker. You can read all about Chris on our About Us Page


So far you have a fresh install of Docker for Windows, which is cool.  However, by default Docker installs a Linux VM to run your containers.  You want to run Windows containers so need to change this.  Luckily Docker makes this easy, but with one potential gotcha.

Locate the Docker icon in the system tray and right click - you will see an option in the menu labelled “Switch to Windows Containers...”

Once you click this, Docker will start the switching process and you will see a “Docker is switching…” message pop up.

After a few moments, Docker will prompt you to enable the Windows Container feature.  Click ok, wait for the install and automated reboot.

When you next log in, Docker will start as normal and you should be all ready to start playing with Windows Containers right? Nope. If you open a PowerShell prompt as Administrator and run the Docker Version command again, you will see that the server “OS/Arch” is still set to “linux/amd64”.  This happens because Docker needs the Container feature installed before it can switch to it.

If you go back to the Docker menu, it will still show the message “Switch to Windows Containers…”.  

Follow the process again and after a while you should get the “Docker is running” pop-up.  To make sure it has switched you can check the Docker Menu - it should look like this:

You can also run the Docker Version command and see the Server “OS/Arch” value, which now shows “windows/amd64”

Now you’re ready to run Windows Containers, which we look at in the next post.


Popular posts from this blog

SQL Server 2012 and Virtual Service Accounts

This post is written by David Postlethwaite
If you are using SQL Server 2012 you will probably have noticed that the default account for the SQL services has changed from that used in previous versions. With SQL 2005 and 2008 the default account for SQL service and SQL Agent service was “NT Authority\System”. This is one the built in accounts on a Windows machine, managed by the machine and selectable from a dedicated dropdown list

The Network Service account was introduced in Windows 2003 as an alternative to using the LocalSystem account, which has full local system privileges on the local machine, a major security concern.
The Network Service has limited local privileges easing these security concerns but when many services on a machine use the Network Service account it becomes harder to track which service is actually accessing resources and performing actions, because all the services are using the one Network Service account.
Also, this account, by default, has sysadmin per…

Always Encrypted

By David Postlethwaite

Always Encrypted is new features in SQL Server 2016 and it is also available in Azure SQL Database. Here you can encrypt columns in a table with a master key and a certificate so that they will appear as encrypted strings to those who don’t have the required certificate installed on their pc.
Once the certificate is installed on the computer then the unencrypted data can then be seen as normal.

The data passes from database to your application as the encrypted value, only the application with the correct certificate can unencrypt the data so it is secure across the wire. This will go some way to resolving the concern of people worried about putting their sensitive data on a shared server in the cloud such as Microsoft Azure and accessing the data across the Internet.

At the time of writing Always Encrypted is only supported with ADO.NET 4.6, JDBC 6.0 and ODBC 13.1 but expect other driver to become available.

The calling application (including SSMS) must also hav…

New in SQL Server 2017: Graph Databases

David has recorded and published a video of his presentation on SQL Server Graph Database. In his video which you can watch below, David provides an excellent introduction into SQL Server 2017 Graph Databases. In his presentation he looks at Tennis results at tournaments for  his favourite player "The Fed"  Rodger Federer.

David  shows how to set up graph database and work with them in SQL Server 2017.

Graph Database is not new. Other vendors have had graph database capabilities for some time so Microsoft are quite late to the market. In David presentation it appears that Microsoft have done a reasonable job of implementing some of the graph database features but he does point some of the limitations of the Microsoft product too and suggests that it is not ready for production yet but Microsoft seem serious about this feature.

Please watch the video and feel free to leave a comment or feedback - David is delivering a version of this talk on Graph databases in SQL Saturday Ka…