When you are working with Docker and you are planning to test something quickly on your workstation… but you are behind a proxy. You fail to pull an image. You fail to build an image. You fail to download from the image. But not anymore after reading this post.
When using Windows containers on Windows 10, you sometimes end up behind a proxy server. Unfortunately, the Docker service does not use the proxy server configured for Windows itself. Instead, it uses the environment variables commonly used on Linux.
[Environment]::SetEnvironmentVariable(“HTTP_PROXY”, “http://1.2.3.4:3128”, [EnvironmentVariableTarget]::Machine) [Environment]::SetEnvironmentVariable(“HTTPS_PROXY”, “http://1.2.3.4:3128”, [EnvironmentVariableTarget]::Machine)
Microsoft is putting a lot of effort in providing a production ready container runtime managed by Docker. Although I am a big fan of containerization, I am a bit worried by the support statement concerning Windows containers.
In my previous post about volumes in Windows containers, I demonstrated how to use volumes to clean up installation files. But I did not answer the question how to use volumes similar to those in Docker for Linux where you can define a volume and add files to it in Dockerfile. Remember it is not possible to create a volume on a non-empty directory in Windows Containers.
When working with Windows containers and volumes, you notice that volumes work differently compared to Docker on Linux. For example, you cannot mount to a non-empty directory. More irritating is the fact that you cannot create a volume on a non-empty directory when working on a Dockerfile. By changing around the instructions, you can use volumes to clean up installation files.
When reading about best practices for creating a Dockerfile, one recommendation is only few layers per image. The reasoning for this approach is that many layers affect performance. I will demonstrate that this is not the case.
In my last post, I presented a generic container for running Minecraft servers. Now, let’s see how to use this container to handle the data inside the container
Half a year ago, I presented a Windows container for running Minecraft servers. In the meantime, I have enhanced the experience and created a generic container which can be used to run Minecraft servers.
When using Rancher for container management, you need to access the host using SSH to debug some strange behaviour. The SSH private key can be downloaded in an archive containing the Docker certificates as well. I have created a tool to download some or all machine configuration archives at once because the GUI only supports downloading them one by one. What is Rancher, you ask? Read on!
This week I talked (in German) about Windows Containers and Docker at DCUG TecCon in Kassel. DCUG is a German Citrix User Group run by Roy Textor which has organized many meetups in Germany. TecCon is the first two-day conference held in the same spirit. Today, I’d like to share the slide deck as well as the code for my demo.