Closed StefanScherer closed 7 years ago
Some more infos. After staring the docker service manually I still have unusual event log entries. Seems like the Event Viewer does not know where to get the correct event log messages. (The description for Event ID 1 from source docker cannot be found.).
Seems there is missing an entry for docker in HKLM:\SYSTEM\CurrentControlSet\Services\EventLog\Application
.
The description for Event ID 1 from source docker cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.
If the event originated on another computer, the display information had to be saved with the event.
The following information was included with the event:
Resolver Setup/Start failed for container none, "json: cannot unmarshal array into Go value of type hcsshim.HNSNetwork"
On another machine I found the entry:
just tested it on 2016 Eval RTM Nano: I had to start the BitsonNano.exe before, import the module, all went through like a charme and after reboot I did not have to register or start a service!
@StefanScherer any chance your machine has a 172.x.x.x IP address? I think the service failed to start due to a HNS problem and that's a common cause.
@PatrickLang That's possible. I'll check tomorrow and test again.
@PatrickLang Indeed, I accidentally used 172.16.32.x
as the internal vCloud app network.
I was able to install Docker in an unattended way with these steps
Install-PackageProvider -Name NuGet -MinimumVersion 2.8.5.201 -Force
Install-Module -Name DockerMsftProvider -Force
Set-PSRepository -InstallationPolicy Trusted -Name PSGallery
Install-Package -Name docker -ProviderName DockerMsftProvider -Force
Set-PSRepository -InstallationPolicy Untrusted -Name PSGallery
Restart-Computer -Force
Docker is up and running after the reboot.
PS: Working on a way to use this package in my packer template https://github.com/StefanScherer/packer-windows/pull/17
Could you explain the problem with a 172... ip address. I have the same problem and a 172... address, but the vEthernet (DockerNAT) adapter is set to 10.0.75.1, so I can't see that there's any kind of conflict. What steps can I take to resolve this?
@jimmymain
So, when the Docker engine is first run on your host it creates a default NAT network with internal IP prefix 172.16.0.0/12. Container endpoints are then automatically attached to this default network, and assigned an IP address from its internal prefix. A problem arises when your container host is in the same IP prefix (172.16.0.0/12)—there is then a conflict between your host and internal prefixes.
You can resolve this be changing the NAT internal IP prefix. To do that, follow these steps:
stop-service docker
Remove-ContainerNetwork nat
3. In your Docker daemon file (C:\ProgramData\Docker\Config\daemon.json), add an entry for fixed-cidr: “a.b.c.d/x”start-service docker
For example, as a result of this change your docker daemon file may look like this:
{
"hosts": [
"npipe://"
],
"fixed-cidr": "204.17.5.0/24"
}
Thanks @kallie-b for the info. Appreciate it.
Cheers, Jay!
I've tried the installer on Win2016 Eval and rebooted. After the reboot the Docker service is not running (ok, there was a warning about starting it manually). I just wonder why this happens because the Service has start type automatic.
I have tried the
Debug-ContainerHost.ps1
script, but this does not retrieve event logs:Looking into the Application event logs I found these two errors from docker:
and