Docker machine timeout - how to fix without destroying the machine?
<p>I'm having a recurring problem with Docker Machine - every few days it decides to timeout and I am unable to recover it once this happens.</p>

<p><strong>Example</strong></p>

<pre><code>docker-machine ls
NAME      ACTIVE   DRIVER       STATE     URL   SWARM   DOCKER   ERRORS
default            virtualbox   Timeout
</code></pre>

<p><strong>Environment Info</strong></p>

<pre><code>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
</code></pre>

<p><strong>Attempted Solutions</strong></p>

<p>I've tried the following things in no particular order:</p>

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

<p><strong>Hack</strong></p>

<p>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.</p>

<pre><code>docker-machine rm -y default &amp;&amp; docker-machine create -d virtualbox default &amp;&amp; eval $(docker-machine env)
</code></pre>

<p><strong>Is there anything I can try?</strong> Thanks!</p>

<hr>

<p><strong>Update: 9th May (Steps to Reproduce)</strong></p>

<p>I can reliably reproduce this problem with the following steps:</p>

<ol>
<li>Start with a freshly created Docker machine.</li>
<li>Use <code>docker-compose up</code> to build some containers.</li>
<li>Shutdown the computer with the containers running.</li>
<li>After reboot the Docker CLI doesn't work due to the Docker machine timing out.</li>
</ol>