Docker Community Forums

Share and learn in the Docker community.

Issues running docker from beta4 update to Beta5


(Frenchben) #1

Expected behavior

Downloaded Beta4 for windows and upgrade to Beta5 - Everything should work properly

Actual behavior

docker ps isn’t working - error is:

Error response from daemon: dial tcp 10.0.75.2:2375: connectex: A connection attempt failed because the connected party
did not properly respond after a period of time, or established connection failed because connected host host has failed to respond.

Information

Fresh windows install -> Installed Beta4 -> Enabled HyperV -> Installed Beta5

PS>[System.Environment]::OSVersion.Version
Major  Minor  Build  Revision
-----  -----  -----  --------
10     0      10586  0
  • DockerDebugInfo.ps1 using Powershell on Windows (command not found)

Logs:

[11:40:27.671][PowerShell     ][Info   ] Run script with parameters: -start True -Credential System.Management.Automation.PSCredential...
[11:40:29.796][HyperV         ][Info   ] Starting VM MobyLinuxVM...
[11:40:29.796][HyperV         ][Info   ] Removing (potentially) existing mount authentication token
[11:40:33.702][HyperV         ][Info   ] Get DNS server address...
[11:40:33.921][HyperV         ][Info   ] Using DNS Servers: 75.75.75.75 75.75.76.76
[11:40:33.936][HyperV         ][Info   ] Wait 5s for MobyLinuxVM to boot...
[11:40:38.928][HyperV         ][Info   ] Setting network configuration of MobyLinuxVM...
[11:40:39.728][HyperV         ][Info   ] Network is configured for MobyLinuxVM
[11:40:39.739][HyperV         ][Info   ] Mounting host filesystem
[11:40:39.821][HyperV         ][Info   ] Mounting with user demo
[11:40:39.846][Notifications  ][Info   ] Docker is running
[11:40:42.858][Proxy          ][Info   ] 2016/03/29 11:40:42 proxy >> GET /v1.22/containers/json
[11:41:03.862][Proxy          ][Info   ] 2016/03/29 11:41:03 dial tcp 10.0.75.2:2375: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
[11:42:35.057][HyperV         ][Info   ] Remove mount on VM MobyLinuxVM
[11:42:35.057][HyperV         ][Info   ] Checking for Hyper-V Windows optional feature
[11:42:35.057][PowerShell     ][Info   ] Run script...
[11:42:36.057][HyperV         ][Info   ] Hyper-V Windows feature is enabled
[11:42:36.057][PowerShell     ][Info   ] Run script with parameters: -RemoveMount True...
[11:42:38.276][HyperV         ][Info   ] Removing (potentially) existing mount authentication token
[11:42:46.055][Updater        ][Info   ] Checking for updates on the Beta channel...
[11:42:46.532][Updater        ][Info   ] Found remote version. Version = 1.10.6.958
[11:42:46.532][Updater        ][Info   ] Local version is up to date.
[11:42:46.532][Notifications  ][Info   ] Docker is up-to-date

Steps to reproduce the behavior


Docker commands not working after upgrade
(Michael Friis) #2

@frenchben The beta4 wouldn’t have worked without hyper-v…? Can you try just un-installing, make sure hyper-v is enabled and then re-install beta5?


(Frenchben) #3

That worked - Does this mean that Beta4 users will need to uninstall prior to getting Beta5?


(Frenchben) #4