All containers and images gone after reboot / update.

[kjlhgfds]

• I have tried with the latest version of my channel (Stable or Edge)
• I have uploaded Diagnostics
• Diagnostics ID: 35294F2F-A6E5-4068-B776-5912C6357EC9/20190731173127

Expected behavior

I install an update / reboot and everything run as usual.

Actual behavior

I installed an update an rebooted and when I run docker container ls or docker images ls the list is empty.

Information

• Is it reproducible ?
  At least for me, I just need to install Docker, run a container, and after a restart of Docker, I can't see the container anymore.

• Is the problem new ?
  Yes, and that's the first time I update.

• Did the problem appear with an update?
  Yes, and / or with a reboot.

• Windows Version: Windows 10 Pro Version 10.0.18362 Build 18362

• Docker Desktop Version: 2.1.0.0 (36874) stable

I'm pretty new to docker so I don't really know what informations you could need but the ones I gave.
If you need anything more, tell me.
Thanks

[kjlhgfds]

Actually, I found something.
After a fresh start of windows and docker, everything is working great.
But if I restart (just) docker, the only container that I can start is lets_encrypt. All the others just start and stop immediatly.

[trung674]

Just updated to version 2.1.0.0, I experienced the same issue

[kjlhgfds]

This is the version and build I have :

Docker Desktop Version: 2.1.0.0 (36874) stable

And this is after doing the update to this version that I had the problem.

[kjlhgfds]

The problem is still here with version 2.1.0.1 (37199).
If it 's usefull, new diagnostics ID : 8921E716-EA0E-453A-99C5-5A28AD4DB979/20190817100143

[docker-robott]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale comment.
Stale issues will be closed after an additional 30d of inactivity.

Prevent issues from auto-closing with an /lifecycle frozen comment.

If this issue is safe to close now please do so.

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

[jlack1987]

/remove-lifecycle stale

Having the same problem here Docker version 19.03.1, build 74b1e89e8a

[egorpavlikhin]

Same here, all images, containers and configuration just gone. The fact that this issue exists and hasn't been fixed in 3 months is very troubling.

[pikkelnut]

I've experience the same issue losing all of my images/containers after upgrading to 2.1.0.5 - Stable (Windows).

[mipe]

I just experienced the same problem with 2.1.0.5 stable.

Had 2 containers running (disk image size 12 GB) and changed Memory from 2048 to 4096 MB and clicked Apply.

Docker restarted immediately and all images were gone (disk image size 60 MB)...

This only happened once so far and I could not reproduce it again.

[pravynandas]

Unfortunately hit the docker restart command now all the images/containers/volumes gone :(. This is very bad experience indeed.

Docker version 19.03.5, build 633a0ea838

[SchatzmanGPS]

The same thing here powered down VM to snapshot and rebooted to no docker containers. Four weeks into a Jenkins project and it is all gone.

[pravynandas]

Can you try restarting the docker service and see? In my case, surprisingly all the containers and volumes are intact after a successful service restart. Prior to that docker commands were running with blank results.

service docker stop
service docker start

[SchatzmanGPS]

Can you try restarting the docker service and see? In my case, surprisingly all the containers and volumes are intact after a successful service restart. Prior to that docker commands were running with blank results.

service docker stop
service docker start

I tried that and the containers didn't start right away. I recognized I had set the flag -rm in my container command. I discovered the folder which holds all of the containers, but it only provides their serialized names. Using that information, I had cause to believe at least one of them was my Jenkins in Docker container. I then ran the command I used to create the containers (removing the -rm flag) and my Jenkins server came back up. It was restored to its previous conditions with all of my user data and projects. This restored the containers back to operation.

[alkampfergit]

Same here, I have a physical machine with Windows 2019, I had some test images, usually it is powered down (is a test server).
Today I've started the server, no images, I needed to doker system clear -a to remove everyting.

The clear command actually found and removed images, but it is annoying

In that instance I've enabled experimental feature to run linux and windows container in the same machine.

[mat007]

Closing in favor of #5278

[maildavc]

your containers did not start automatically.

u need "sudo docker ps -a" to list them and then start all of them manually.

[query1280]

I have same experience too.
I'm using ubuntu 20.04 LTS
Client: Docker Engine - Community
Version: 19.03.8
API version: 1.39 (downgraded from 1.40)
Go version: go1.12.17
Git commit: afacb8b7f0
Built: Wed Mar 11 01:25:46 2020
OS/Arch: linux/amd64
Experimental: false

Server:
Engine:
Version: 18.09.9
API version: 1.39 (minimum version 1.12)
Go version: go1.13.4
Git commit: 9552f2b
Built: Sat Nov 16 01:07:48 2019
OS/Arch: linux/amd64
Experimental: false

I have no idea why this happened. All I've done were erased..

[markusheinemann]

For me restarting the docker service solved the problem. I run in the same issue after updating docker on windows.

[JIBSIL]

Restart the docker service, worked for me!

[bkstha]

I have the same problem but restart docker works for me.
The strange thing is that when I use the hard drive the problem doesn't occur, but when I use SSD I have to restart docker after every reboot of my server.
What may be the cause? Any solution for this?
Components:
raspberrypi 4
rasbian os 32bit
openmediavault

[flufy3d]

I have the same problem
Docker version 19.03.8, build afacb8b7f0
Linux kenshin 5.4.0-40-generic #44-Ubuntu SMP Tue Jun 23 00:01:04 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

the current workaround is
sudo systemctl restart docker

[lezli01]

Problem occurs for me as well.
I have a fresh Ubuntu Server 20.04 LTS, installed latest docker.ce package and everything stated on official docker installation guide.

After a reboot the lists of docker image ls or docker container ls are empty but my containers that are configured to autostart are running. The only solution for me currently is to restart the service using sudo service docker restart but that restarts the containers and that is not really a good approach for example for my jenkins server.

[lezli01]

I finally solved this issue, in my case it was a snap docker package which was installed by ubuntu server installer. I remember ticking the checkbox when it asked me do I want docker to be installed, it seems it installs a snap package and that version has issues. After removing snap sudo snap remove docker version everything worked fine.

[p5a0u9l]

Same exact issue as @lezli01. Can confirm that sudo snap remove docker + reboot and re-issuing docker-compose up -d resolved the issue such that rebooting does not require sudo systemctl restart docker

[docker-robott]

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