Running docker container disappears after host reboot; leaving file system behind

deftdawg commented 5 years ago

Last night my Windows host rebooted itself to apply a company pushed update.

Following that restart, the container I had been running disappeared completely from Docker, it's not present in docker ps -a and there are no docker logs <container_id> logs; fortunately the overlay filesystem is still present, so the data is not gone.

The purpose of this issue threefold:

Note that this container loss bug occurred
Ask is there a workaround to recreate the lost container?
let persons who experience this issue to look for any data they care about from the vanished container by the following steps:

docker-machine ssh
sudo su - # change to root
cd /mnt/sda1/var/lib/docker/overlay2/<container_id>/diff/<sub_folder of what you care about>
# or if you don't know the container id search for a file you created
find /mnt/sda1/var/lib/docker/overlay2/ | grep file_I_care_about
cp <files_you_care_about> to /c/Users/<Windows user>/Desktop

System specs: Windows 10 Pro OS Version: 10.0.17763 N/A Build 17763 Docker version: 18.09.5

ziplock9000 commented 5 years ago

It's happened to me 3 times in the last hour while trying to set up Gitlabs-CE on Windows Docker. It gives me absolutely no confidence in this software at all when it can catastrophically evaporate like this.

50bbx commented 5 years ago

I had the same issue with a super simple docker container running a mysql server. docker ps -a doesn't list the container.

hallicarnassus commented 5 years ago

Same here, the images however persist

ab316 commented 4 years ago

I am facing the same issue. My specs:

Client: Docker Engine - Community Version: 19.03.5 API version: 1.40 Go version: go1.12.12 Git commit: 633a0ea Built: Wed Nov 13 07:22:37 2019 OS/Arch: windows/amd64 Experimental: false

Server: Docker Engine - Community Engine: Version: 19.03.5 API version: 1.40 (minimum version 1.12) Go version: go1.12.12 Git commit: 633a0ea Built: Wed Nov 13 07:29:19 2019 OS/Arch: linux/amd64 Experimental: false containerd: Version: v1.2.10 GitCommit: b34a5c8af56e510852c35414db4c1f4fa6172339 runc: Version: 1.0.0-rc8+dev GitCommit: 3e425f80a8c931f88e6d94a8c831b9d5aa481657 docker-init: Version: 0.18.0 GitCommit: fec3683

docker-archive / toolbox

Running docker container disappears after host reboot; leaving file system behind #836