I have 33 containers (via docker ps -a) and 619 images (via docker images -a) while running docker daemon v1.9.1. My /var/lib/docker directory is 39.3G (via sudo du -hs /var/lib/docker from inside my docker-machine). When I do the upgrade via docker-machine upgrade dev or when I run the migrator manually from inside my docker-machine using docker run --rm -v /var/lib/docker:/var/lib/docker docker/v1.10-migrator, I get some 622 lines or so of output that all happens within just a few seconds. From what I've been reading, it seems like it should be taking way longer than just a few seconds. When the migration is all finished and I'm running docker daemon v1.10, I get no containers from docker ps -a and I have only a small handful of images.
All that being said, I first attempted the upgrade without even knowing it when I did a docker-machine upgrade dev a week or so ago. After that finished, I tried doing some docker command (probably a simple docker ps) and it appeared to be hung (since I had no idea that the upgrade was migrating my images and containers). I gave it a minute or two and then decided that a system reboot would clear up the issue, so I rebooted my computer. Perhaps I'm stuck in some sort of in between migration state where docker has some stored information some place that says, "Yeah, we did the upgrade," but my images and containers actually aren't fully upgraded? If so, how can I undo whatever has been done and start the migration from scratch again?
I have 33 containers (via
docker ps -a) and 619 images (viadocker images -a) while running docker daemon v1.9.1. My/var/lib/dockerdirectory is 39.3G (viasudo du -hs /var/lib/dockerfrom inside my docker-machine). When I do the upgrade viadocker-machine upgrade devor when I run the migrator manually from inside my docker-machine usingdocker run --rm -v /var/lib/docker:/var/lib/docker docker/v1.10-migrator, I get some 622 lines or so of output that all happens within just a few seconds. From what I've been reading, it seems like it should be taking way longer than just a few seconds. When the migration is all finished and I'm running docker daemon v1.10, I get no containers fromdocker ps -aand I have only a small handful of images.All that being said, I first attempted the upgrade without even knowing it when I did a
docker-machine upgrade deva week or so ago. After that finished, I tried doing some docker command (probably a simpledocker ps) and it appeared to be hung (since I had no idea that the upgrade was migrating my images and containers). I gave it a minute or two and then decided that a system reboot would clear up the issue, so I rebooted my computer. Perhaps I'm stuck in some sort of in between migration state where docker has some stored information some place that says, "Yeah, we did the upgrade," but my images and containers actually aren't fully upgraded? If so, how can I undo whatever has been done and start the migration from scratch again?