Machine: Machine status marked as 'Timeout' after host reboot with running containers

[saikojosh]

If the host machine is shutdown with any containers running the Docker machine will have a status of 'timeout' when the host is rebooted. This appears to be irreversible. The only solution I've found is to destroy the Docker machine and recreate it from scratch.

Related? Machine status marked as 'Timeout' after host suspend ended with Virtualbox

Example

docker-machine ls
NAME      ACTIVE   DRIVER       STATE     URL   SWARM   DOCKER   ERRORS
default            virtualbox   Timeout

Environment Info

uname -a                 Darwin ColeyMBPR 15.4.0 Darwin Kernel Version 15.4.0: Fri Feb 26 22:08:05 PST 2016; root:xnu-3248.40.184~3/RELEASE_X86_64 x86_64
docker version           1.11.0
docker-machine version   0.7.0
vboxmanage --version     5.0.20r106931

Attempted Solutions

I've tried the following things in no particular order:

• Restarting the docker machine.
• Running eval "$(docker-machine env default)"
• Regenerating the certificates docker-machine regenerate-certs default
• Restarting my host box.
• Upgrading Docker.
• Reinstalling Docker.
• Upgrading VirtualBox.
• Removing all VirtualBox host-only network devices.

Hack

The only thing that's working for me right now is destroying the docker machine and recreating it. This destroys all my images and containers, and it's incredibly time consuming to set it up again.

docker-machine rm -y default && docker-machine create -d virtualbox default && eval $(docker-machine env)

Steps to Reproduce

I can reliably reproduce this problem with the following steps:

1. Start with a freshly created Docker machine.
2. Use docker-compose up to build some containers.
3. Shutdown the computer with the containers running.
4. After reboot the Docker CLI doesn't work due to the Docker machine timing out.

Now I've discovered what's causing the problem I'll make sure I kill all containers at the end of the day and see if the problem is resolved.

[jdcaballerov]

I am having the same issue with machines created with other drivers than virtualbox :S. There is also a question about it on stackoverflow

I was once able to get it back working but I am not able to reproduce. I tried everything and after a host reboot it worked again.

It is important to add that ssh is possible, even after cert renewal.

[saikojosh]

Upgrading to Docker Beta solved this problem for me.

On 24 May 2016, at 17:20, jdcaballerov [email protected] wrote:

I am having the same issue with machines created with other drivers than virtualbox :S. There is also a question about it on stackoverflow https://stackoverflow.com/questions/37069718/docker-machine-timeout-how-to-fix-without-destroying-the-machine
I was once able to get it back working but I am not able to reproduce. I tried everything and after a host reboot it worked again.

It is important to add that ssh is possible, even after cert renewal.

—
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub https://github.com/docker/machine/issues/3418#issuecomment-221325177

[zz22394]

I got the same error message when connected with my company's VPN,
and resolved it by disconnecting the VPN.

Error message:

[sso@MBP ~]$ docker-machine ls
NAME      ACTIVE   DRIVER       STATE     URL   SWARM   DOCKER   ERRORS
default            virtualbox   Timeout
[sso@MBP ~]$


[sso@MBP ~]$ docker-machine regenerate-certs default
Regenerate TLS machine certs?  Warning: this is irreversible. (y/n): y
Regenerating TLS certificates
Waiting for SSH to be available...
Detecting the provisioner...
Copying certs to the local machine directory...
Copying certs to the remote machine...
Setting Docker configuration on the remote daemon...

This machine has been allocated an IP address, but Docker Machine could not
reach it successfully.

SSH for the machine should still work, but connecting to exposed ports, such as
the Docker daemon port (usually <ip>:2376), may not work properly.

You may need to add the route manually, or use another related workaround.

This could be due to a VPN, proxy, or host file configuration issue.

You also might want to clear any VirtualBox host only interfaces you are not using.
[sso@MBP ~]$

[bad5anta]

Same issue here.

uname -a                 Linux lapland 3.19.0-65-generic #73~14.04.1-Ubuntu SMP Wed Jun 29 21:05:22 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux
Docker version           1.11.2, build b9f10c9
docker-machine version   0.7.0, build a650a40
vboxmanage --version     5.1.0r108711

[ivandir]

@zz22394 This definitely a VPN problem. I executed both the docker-machine regenerate-certs and create commands without the VPN being on and it worked.

[ohcrider]

same here

Version 1.13.1 (15353)
Channel: Stable
94675c5a76

[hadilu]

Proxifier would cause the same problem. Try to create a new direct rule will solve it.