Failed to deploy 'Compose: docker-compose.yml': Some services/containers not started I am using debian 9 with docker1.13.1. I can do a 'docker-compose up' and it works. When you execute the command, sudo systemctl start docker, it creates a docker process. That docker process contains dockerd daemon thread. The command also creates default docker.sock Unix socket. The docker.sock socket is continuously listened by dockerd daemon thread. This makes you can do kernel-level IPC with docker.pid process.

So, pretty much the first thing I did when the Windows 10 Anniversary Edition was installed onto my primary development machine was to installer the Windows Container Service and Docker on it. I used the to perform the installation. This is the same method I’d been using on my secondary development machine (running Insider Preview builds) since it was first available in build 14372. Note: The Windows Containers on Windows 10 Quick Start guide doesn’t mention the Anniversary Edition specifically, but the method still works.

Unfortunately though, this time it didn’t work. When I attempted to start the Docker Service I received the error: start-service: Failed to start service 'Docker Engine (docker)'.

So, after a bit of digging around I found the following error in the Windows Event Log in the Application logs: Basically what this was telling me was that the Docker Daemon couldn’t create the new virtual network adapter that it needed – because it already existed. So a quick run of Get-NetAdapter and I found that the docker adapter “vEthernet (HNS Internal)” already existed: So what I needed to do was uninstall this adapter so that the Docker Service could recreate it. I’m not actually aware of a command line method of doing (except for using ) so I had to resort to using Device Manager: You’ll need to use the output of the Get-NetAdapter to find he right adapter uninstall. Once it has been uninstalled you should be able to start the service again: This time the service should start successfully. A quick call to docker ps shows that the container service is indeed working. So now I can get onto the process pulling down the base container images.

Hopefully if anyone else runs into this problem in Windows 10 AE this will help them resolve it. Thanks for posting.

I had almost the same error: fatal: Error starting daemon: Error initializing network controller: Error creating default network: HNS failed with error: The parameter is incorrect. Turns out that in playing around in Windows 10 new NAT features I had created a NAT visible in Hyper-V. Removing the internal switch from Hyper-V did not help. Running Get-NetNat Remove-NetNat did the trick and dockerd starts. The reason is that only one Internal NAT is allowed on Windows 10, I think 🙂 Like.

Microsoft Most Valuable Professional 2017 award in Cloud and Datacenter Management. Adobe flash 9.0 free download.