no images and containers after update to 1.12.0-beta21 (build 5971) about for-win HOT 6 CLOSED

Thanks for the report and apologies that you lost the images and containers. Normally, the installer does not overwrite existing containers/images, but it seems that the installer detected an Docker Toolbox image somewhere and offered to migrate that. We are considering to disable the Toolbox migration when updating from one Docker for Windows version to a newer one.

from for-win.

Fortunately I was just about to get started with "Docker for Windows", so there was no harm.
I remember that I got the same question already before. Can you tell me on Win10, where exactly this "default"-docker from toolbox is installed or in which way "Docker for Windows" detects it? I'd like to get rid of the old stuff completely since I realized that lots of errors are coming from these "old relicts" hidden deep in the system.

from for-win.

By default it looks in ~\.docker\machines\machine\default\disk.vmdk

from for-win.

hm... nothing there and anywhere else to find. I'll pass that "find toolbox-residues" issue to the esoterism-department :)

from for-win.

You just have to delete ~\.docker to get rid of old toolbox VMs

from for-win.

Closed issues are locked after 30 days of inactivity.
This helps our team focus on active issues.

If you have found a problem that seems similar to this, please open a new issue.

Send feedback to Docker Community Slack channels #docker-for-mac or #docker-for-windows.
/lifecycle locked

from for-win.