-
Notifications
You must be signed in to change notification settings - Fork 85
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Docker 20.10 daemon takes 5 minutes to start after reboot #1162
Comments
What's in the daemon logs? You can check this in |
The system started at 16:28, but the logs for docker does not appear until 16:33. journalctl -u docker shows
|
This might be related to moby/moby#41767 |
Indeed this is very similar to the problem described in moby/moby#41767. I had a service that required docker.service but not after docker.
This service caused the 5 minutes delay in multi-user.target. After the failure of this service in 5 minutes, docker.service started up correctly. After I added the line to start my app after docker.service
docker.service starts normally but my service never starts up. The culprit seems to be the line in docker.service,
The circular dependency really confuses systemd. |
The problem went away after reverting the changes introduced in 20.10.3 in I removed |
Thanks for verifying; let me close this ticket as a duplicate of moby/moby#41767, to keep everything in a single place 👍 |
Docker 20.10.1 was released, which contains an updated systemd unit to fix this issue |
Expected behavior
Docker daemon starts immediately after system reboot and available.
Actual behavior
Docker daemon is stuck for 5 minutes after reboot. No containers can be started. After 5 minutes, all seems to be OK.
Reverting docker-ce to 19.03.14 fixes the problem, the daemon starts immediately and containers can be started.
Steps to reproduce the behavior
Install docker-ce 20.10.0 on Ubuntu 20.04.1, then reboot.
After reboot, the command "docker ps" is stuck for almost 5 minutes. Any docker-cli commands are all stuck during this time.
Output of
docker version
:Output of
docker info
:Additional environment details (AWS, VirtualBox, physical, etc.)
This is a physical server.
I can also reproduce this easily on a virtual server running in kvm, only difference seems to be that on the virtual server, I waited about 2 minutes for docker to start.
The text was updated successfully, but these errors were encountered: