The meetup yesterday was excellent. I was very happy because participants asked many great questions which means they felt this is an interesting topic. I enjoy it too and I would like to say thank you for all who were there and who supported me.
Additionally you can find here the presentation:
Wednesday, Mar 23 – Budapest, Hungary
Docker (on Windows) – How to avoid traps by Tibor Kiss Windows Server 2016 is the first windows which natively supports the Containers. I am sure many of you have already met with articles about this topic. Now we would like to provide you an overview regarding: – how can we avoid tumblers at the very first time – how can we cope with difficulties which are provided by the current version – some Docker containers use cases
Here you can find some observations about Docker on Windows.
| Observatons and tips about Docker on Windows | |
|---|---|
| After you start a container with the -a switch “docker start -a <container name>” then you want to use “docker exec -it <container name> powershell” although it is enter the container it is frozen. Without -a everithing is fine. | |
| When you create a container pelase rename it with this command: Rename-Computer -NewName $oNewContainerName . Then please restart the docker container. If you miss this your container won’t start any more after a Docker host restart. | |
| Configuration file in Windows: “C:\ProgramData\Docker\Containers\<GUID of container>\config.json” és “C:\ProgramData\Docker\Containers\<GUID of container>\hostconfig.json“ | |
| Please make a copy from the configuration files. That could be usefull when yor container does not want to start adfter a Docker host restart. When you meet this message: “Win32 API call returned error r1=2147942452 err=You were not connected because a duplicate name exists on the network. If joining a domain, go to System in Control Panel to change the computer name and try again.” you merely need to overwrite the config files from backup then your container will start correctly.
Other workaround to fix your containers:
|
|
| Windows Feature installation. When you want to install/add/enable a new feature in Windows it required the installation media. Especially the SXS dorectory from installation media. In this case the usage of our powershell command:
Add-WindowsFeature <comma separated feature list> -Source “<Path of installation media>\sources\sxs” |
|
| The DEL does not work in Docker console. You must use Backspace instead of DEL. | |
Feel free to get in touch with any comment, feedback or questions.
Since we know the Windows Server 2016 will support the Containers (Docker) we are very happy and exciting. We want to test and see how it works on Windows. Now we can use Windows Server 2016 TP4 as a great foundation.
This article shows some commands which useful when you work with Docker on windows and Windows Containers