Container connectivity lost after switching wireless networks

[egoldschmidt]

This has been brought up a few times but no one seems to have suggested a solution or workaround. It's a pretty serious impediment to local development as you constantly have to wrestle with the possibility that your container no longer has connectivity. Exception messages are super opaque and confuse other members of the team with less experience using Docker. Is there any timeline for a fix, generally accepted workaround, or even description of the root cause?

[provegard]

+1

Although this may be a VirtualBox problem - I have had this problem with VirtualBox VMs in general.

As a workaround - is it possible to restart networking inside boot2docker in some way?

[jakirkham]

+1

Also, I know that Vagrant use to have this problem, but does not any more. They also use VirtualBox. So, a solution should be possible.