Disable automatic updates of Docker Toolbox

[FedericoRuiz1]

Today I started Docker Toolbox in windows, without asking me nor any prompts whatsoever it updated to the latest version of Docker Toolbox, and in doing so it deleted all my locally saved images and running containers.

So now I find myself pulling a several GB large image from the Docker Hub ( which will take several hours given the already documented issue of Docker's download speed getting progressively slower when pulling big layers), all because Docker Toolbox updated automatically.

Either have Docker not delete locally saved images when its updated, or ask the user whether they want to update beforehand.

[LHCGreg]

+1, after 2 automatic updates I now have 3 VMs displayed in VirtualBox, with 2 of them inaccessible with an error message like

Machine UUID {3d95bdeb-96fe-48ed-92a2-e58dd61086cc} in 'C:\Users\najdag.DBRS2\.docker\machine\machines\default\default\default.vbox' doesn't match its UUID {bc958536-1554-4877-b691-f9b1310a0257} in the registry file 'C:\Users\najdag.DBRS2/.VirtualBox\VirtualBox.xml'.
Result Code: 
E_FAIL (0x80004005)
Component: 
MachineWrap
Interface: 
IMachine {f30138d4-e5ea-4b3a-8858-a059de4c93fd}

(the only difference between the messages for the 2 VMs is the second UUID ("doesn't match its UUID {.....}").

After an automatic update, I lose any containers I had!

[talktejas]

This is a serious issue. I have exactly the same issue where docker wiped off old images and recreated new ones. It is unfortunate that docker blames this on virtualbox and does nothing about it ....

This makes docker unreliable

[cmarquardt]

Same here. The docker startup script (Docker Toolbox on Windows) printed out a message saying there's a new boot2docker.iso available and immediately started to download create a new default VM from it. The old one, of course, got deleted, including all containers and volumes inside.

I appreciate an option to the update the VM, but I don't think it makes sense to happen automatically.

[Zenopheus]

This approach to updating is causing problems in professional installations. Asking a user (who might not even know what Docker is) in a customized environment to update can lead to costly support and testing issues. Not to mention this trend of forcing software updates on people needs to end.

As a compromise I recommend an interface change:

Note: "Not Now" is the same as "Remind me later" but was renamed so it works better with the checkboxes.