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:
Client: Docker Engine - Community
Version: 20.10.0
API version: 1.41
Go version: go1.13.15
Git commit: 7287ab3
Built: Tue Dec 8 18:59:40 2020
OS/Arch: linux/amd64
Context: default
Experimental: true
Server: Docker Engine - Community
Engine:
Version: 20.10.0
API version: 1.41 (minimum version 1.12)
Go version: go1.13.15
Git commit: eeddea2
Built: Tue Dec 8 18:57:45 2020
OS/Arch: linux/amd64
Experimental: false
containerd:
Version: 1.4.3
GitCommit: 269548fa27e0089a8b8278fc4fc781d7f65a939b
runc:
Version: 1.0.0-rc92
GitCommit: ff819c7e9184c13b7c2607fe6c30ae19403a7aff
docker-init:
Version: 0.19.0
GitCommit: de40ad0
Output of docker info:
Client:
Context: default
Debug Mode: false
Plugins:
app: Docker App (Docker Inc., v0.9.1-beta3)
buildx: Build with BuildKit (Docker Inc., v0.4.2-docker)
Server:
Containers: 1
Running: 1
Paused: 0
Stopped: 0
Images: 5
Server Version: 20.10.0
Storage Driver: overlay2
Backing Filesystem: extfs
Supports d_type: true
Native Overlay Diff: true
Logging Driver: json-file
Cgroup Driver: cgroupfs
Cgroup Version: 1
Plugins:
Volume: local
Network: bridge host ipvlan macvlan null overlay
Log: awslogs fluentd gcplogs gelf journald json-file local logentries splunk syslog
Swarm: inactive
Runtimes: io.containerd.runtime.v1.linux runc io.containerd.runc.v2
Default Runtime: runc
Init Binary: docker-init
containerd version: 269548fa27e0089a8b8278fc4fc781d7f65a939b
runc version: ff819c7e9184c13b7c2607fe6c30ae19403a7aff
init version: de40ad0
Security Options:
apparmor
seccomp
Profile: default
Kernel Version: 5.4.0-56-generic
Operating System: Ubuntu 20.04.1 LTS
OSType: linux
Architecture: x86_64
CPUs: 48
Total Memory: 377.8GiB
Name: REDACTED
ID: SJDV:CLNU:LI5U:4KK3:6K5N:CZH2:WYNQ:SSK3:S57L:L2BM:N4BL:64RB
Docker Root Dir: /var/lib/docker
Debug Mode: false
Registry: https://index.docker.io/v1/
Labels:
Experimental: false
Insecure Registries:
127.0.0.0/8
Live Restore Enabled: false
WARNING: No swap limit support
WARNING: No blkio weight support
WARNING: No blkio weight_device support
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.
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.