How to recover removed Docker images/containers after upgrading Docker Toolbox on Windows 7?
I had installed Docker Toolbox 18.03.0-ce on Windows 7 64-bit and had many pulled images and built containers. After upgrading Docker Toolbox to 18.09.1, there are no images and containers in results of these listings, but my networks, volumes and used space in Boot2Docker are as the same as before:
$ docker images --all
REPOSITORY TAG IMAGE ID CREATED SIZE
$ docker container ls --all
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
$ docker network ls
NETWORK ID NAME DRIVER SCOPE
446f56b6ddde bridge bridge local
7ec9271f1395 downloads_default bridge local
d35c380fb35e host host local
12beb20e048f none null local
af4825df71cd temp_default bridge local
2b91271536ac net1_default bridge local
...
$ docker volume ls
DRIVER VOLUME NAME
local c1a0b6eaea1d9bffa8ea1cff67fae47517f6cde6e7ff875c5264aba3a422a777
local docker1_data
local downloads_data
...
The old Docker Machine is also running as the same as before:
$ docker-machine.exe ls
NAME ACTIVE DRIVER STATE URL SWARM DOCKER ERRORS
default * virtualbox Running tcp://192.168.99.100:2376 v18.06.1-ce
But the size of the virtual disk of Boot2Docker is still 15GB:
$ ls -lh /c/Users/hamid/.docker/machine/machines/default/disk.vmdk
-rw-r--r-- 1 99777 1049089 15G Jan 20 11:41 /c/Users/hamid/.docker/machine/machines/default/disk.vmdk
Also in the running Boot2Docker, /mnt/sda1/var/lib/docker/aufs
has 10.6GB size:
root@default:/# du -d1 -h /mnt/sda1/var/lib/docker
20.0K /mnt/sda1/var/lib/docker/builder
36.1M /mnt/sda1/var/lib/docker/image
20.0K /mnt/sda1/var/lib/docker/plugins
8.0K /mnt/sda1/var/lib/docker/overlay2
4.0K /mnt/sda1/var/lib/docker/tmp
270.7M /mnt/sda1/var/lib/docker/volumes
672.0K /mnt/sda1/var/lib/docker/containerd
72.0K /mnt/sda1/var/lib/docker/buildkit
4.0K /mnt/sda1/var/lib/docker/trust
136.0K /mnt/sda1/var/lib/docker/network
4.0K /mnt/sda1/var/lib/docker/runtimes
4.0K /mnt/sda1/var/lib/docker/swarm
10.6G /mnt/sda1/var/lib/docker/aufs
3.9M /mnt/sda1/var/lib/docker/containers
10.9G /mnt/sda1/var/lib/docker
The main large folder is /mnt/sda1/var/lib/docker/aufs/diff
that has about 300 folders. It seems that old files are still there. Is there any way to recover images or containers back?
windows docker docker-toolbox
add a comment |
I had installed Docker Toolbox 18.03.0-ce on Windows 7 64-bit and had many pulled images and built containers. After upgrading Docker Toolbox to 18.09.1, there are no images and containers in results of these listings, but my networks, volumes and used space in Boot2Docker are as the same as before:
$ docker images --all
REPOSITORY TAG IMAGE ID CREATED SIZE
$ docker container ls --all
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
$ docker network ls
NETWORK ID NAME DRIVER SCOPE
446f56b6ddde bridge bridge local
7ec9271f1395 downloads_default bridge local
d35c380fb35e host host local
12beb20e048f none null local
af4825df71cd temp_default bridge local
2b91271536ac net1_default bridge local
...
$ docker volume ls
DRIVER VOLUME NAME
local c1a0b6eaea1d9bffa8ea1cff67fae47517f6cde6e7ff875c5264aba3a422a777
local docker1_data
local downloads_data
...
The old Docker Machine is also running as the same as before:
$ docker-machine.exe ls
NAME ACTIVE DRIVER STATE URL SWARM DOCKER ERRORS
default * virtualbox Running tcp://192.168.99.100:2376 v18.06.1-ce
But the size of the virtual disk of Boot2Docker is still 15GB:
$ ls -lh /c/Users/hamid/.docker/machine/machines/default/disk.vmdk
-rw-r--r-- 1 99777 1049089 15G Jan 20 11:41 /c/Users/hamid/.docker/machine/machines/default/disk.vmdk
Also in the running Boot2Docker, /mnt/sda1/var/lib/docker/aufs
has 10.6GB size:
root@default:/# du -d1 -h /mnt/sda1/var/lib/docker
20.0K /mnt/sda1/var/lib/docker/builder
36.1M /mnt/sda1/var/lib/docker/image
20.0K /mnt/sda1/var/lib/docker/plugins
8.0K /mnt/sda1/var/lib/docker/overlay2
4.0K /mnt/sda1/var/lib/docker/tmp
270.7M /mnt/sda1/var/lib/docker/volumes
672.0K /mnt/sda1/var/lib/docker/containerd
72.0K /mnt/sda1/var/lib/docker/buildkit
4.0K /mnt/sda1/var/lib/docker/trust
136.0K /mnt/sda1/var/lib/docker/network
4.0K /mnt/sda1/var/lib/docker/runtimes
4.0K /mnt/sda1/var/lib/docker/swarm
10.6G /mnt/sda1/var/lib/docker/aufs
3.9M /mnt/sda1/var/lib/docker/containers
10.9G /mnt/sda1/var/lib/docker
The main large folder is /mnt/sda1/var/lib/docker/aufs/diff
that has about 300 folders. It seems that old files are still there. Is there any way to recover images or containers back?
windows docker docker-toolbox
add a comment |
I had installed Docker Toolbox 18.03.0-ce on Windows 7 64-bit and had many pulled images and built containers. After upgrading Docker Toolbox to 18.09.1, there are no images and containers in results of these listings, but my networks, volumes and used space in Boot2Docker are as the same as before:
$ docker images --all
REPOSITORY TAG IMAGE ID CREATED SIZE
$ docker container ls --all
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
$ docker network ls
NETWORK ID NAME DRIVER SCOPE
446f56b6ddde bridge bridge local
7ec9271f1395 downloads_default bridge local
d35c380fb35e host host local
12beb20e048f none null local
af4825df71cd temp_default bridge local
2b91271536ac net1_default bridge local
...
$ docker volume ls
DRIVER VOLUME NAME
local c1a0b6eaea1d9bffa8ea1cff67fae47517f6cde6e7ff875c5264aba3a422a777
local docker1_data
local downloads_data
...
The old Docker Machine is also running as the same as before:
$ docker-machine.exe ls
NAME ACTIVE DRIVER STATE URL SWARM DOCKER ERRORS
default * virtualbox Running tcp://192.168.99.100:2376 v18.06.1-ce
But the size of the virtual disk of Boot2Docker is still 15GB:
$ ls -lh /c/Users/hamid/.docker/machine/machines/default/disk.vmdk
-rw-r--r-- 1 99777 1049089 15G Jan 20 11:41 /c/Users/hamid/.docker/machine/machines/default/disk.vmdk
Also in the running Boot2Docker, /mnt/sda1/var/lib/docker/aufs
has 10.6GB size:
root@default:/# du -d1 -h /mnt/sda1/var/lib/docker
20.0K /mnt/sda1/var/lib/docker/builder
36.1M /mnt/sda1/var/lib/docker/image
20.0K /mnt/sda1/var/lib/docker/plugins
8.0K /mnt/sda1/var/lib/docker/overlay2
4.0K /mnt/sda1/var/lib/docker/tmp
270.7M /mnt/sda1/var/lib/docker/volumes
672.0K /mnt/sda1/var/lib/docker/containerd
72.0K /mnt/sda1/var/lib/docker/buildkit
4.0K /mnt/sda1/var/lib/docker/trust
136.0K /mnt/sda1/var/lib/docker/network
4.0K /mnt/sda1/var/lib/docker/runtimes
4.0K /mnt/sda1/var/lib/docker/swarm
10.6G /mnt/sda1/var/lib/docker/aufs
3.9M /mnt/sda1/var/lib/docker/containers
10.9G /mnt/sda1/var/lib/docker
The main large folder is /mnt/sda1/var/lib/docker/aufs/diff
that has about 300 folders. It seems that old files are still there. Is there any way to recover images or containers back?
windows docker docker-toolbox
I had installed Docker Toolbox 18.03.0-ce on Windows 7 64-bit and had many pulled images and built containers. After upgrading Docker Toolbox to 18.09.1, there are no images and containers in results of these listings, but my networks, volumes and used space in Boot2Docker are as the same as before:
$ docker images --all
REPOSITORY TAG IMAGE ID CREATED SIZE
$ docker container ls --all
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
$ docker network ls
NETWORK ID NAME DRIVER SCOPE
446f56b6ddde bridge bridge local
7ec9271f1395 downloads_default bridge local
d35c380fb35e host host local
12beb20e048f none null local
af4825df71cd temp_default bridge local
2b91271536ac net1_default bridge local
...
$ docker volume ls
DRIVER VOLUME NAME
local c1a0b6eaea1d9bffa8ea1cff67fae47517f6cde6e7ff875c5264aba3a422a777
local docker1_data
local downloads_data
...
The old Docker Machine is also running as the same as before:
$ docker-machine.exe ls
NAME ACTIVE DRIVER STATE URL SWARM DOCKER ERRORS
default * virtualbox Running tcp://192.168.99.100:2376 v18.06.1-ce
But the size of the virtual disk of Boot2Docker is still 15GB:
$ ls -lh /c/Users/hamid/.docker/machine/machines/default/disk.vmdk
-rw-r--r-- 1 99777 1049089 15G Jan 20 11:41 /c/Users/hamid/.docker/machine/machines/default/disk.vmdk
Also in the running Boot2Docker, /mnt/sda1/var/lib/docker/aufs
has 10.6GB size:
root@default:/# du -d1 -h /mnt/sda1/var/lib/docker
20.0K /mnt/sda1/var/lib/docker/builder
36.1M /mnt/sda1/var/lib/docker/image
20.0K /mnt/sda1/var/lib/docker/plugins
8.0K /mnt/sda1/var/lib/docker/overlay2
4.0K /mnt/sda1/var/lib/docker/tmp
270.7M /mnt/sda1/var/lib/docker/volumes
672.0K /mnt/sda1/var/lib/docker/containerd
72.0K /mnt/sda1/var/lib/docker/buildkit
4.0K /mnt/sda1/var/lib/docker/trust
136.0K /mnt/sda1/var/lib/docker/network
4.0K /mnt/sda1/var/lib/docker/runtimes
4.0K /mnt/sda1/var/lib/docker/swarm
10.6G /mnt/sda1/var/lib/docker/aufs
3.9M /mnt/sda1/var/lib/docker/containers
10.9G /mnt/sda1/var/lib/docker
The main large folder is /mnt/sda1/var/lib/docker/aufs/diff
that has about 300 folders. It seems that old files are still there. Is there any way to recover images or containers back?
windows docker docker-toolbox
windows docker docker-toolbox
asked Jan 20 at 9:25
Hamid RohaniHamid Rohani
79911323
79911323
add a comment |
add a comment |
0
active
oldest
votes
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f54275080%2fhow-to-recover-removed-docker-images-containers-after-upgrading-docker-toolbox-o%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f54275080%2fhow-to-recover-removed-docker-images-containers-after-upgrading-docker-toolbox-o%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown