Description
After upgrading docker-ce to 20.10.x, reboot/shutdown the machine hangs 90s due to containerd-shim.
[ OK ] Reached target Shutdown.
[ OK ] Reached target Final Step.
[ OK ] Finished Reboot.
[ OK ] Reached target Reboot.
[ 214.337805] systemd-shutdown[1]: Waiting for process: containerd-shim
Steps to reproduce the issue:
- fresh install docker-ce from download.docker.com on Ubuntu 20.04 LTS
- enable live-restore
docker run -d k8s.gcr.io/pausesudo reboot
Describe the results you received:
The shutdown/reboot process stuck for 90s, due to containerd-shim.
Describe the results you expected:
containerd-shim should not interfere with shutdown/reboot process.
Additional information you deem important (e.g. issue happens only occasionally):
Since #41210, the default runtime is runc v2. The old runc v1 runtime does not have this issue. Tested with the following commands.
docker run -d --name runc-v1 --runtime=io.containerd.runtime.v1.linux k8s.gcr.io/pause
docker run -d --name runc-v2 --runtime=io.containerd.runc.v2 k8s.gcr.io/pause
Output of docker version:
Client: Docker Engine - Community
Version: 20.10.1
API version: 1.41
Go version: go1.13.15
Git commit: 831ebea
Built: Tue Dec 15 04:34:58 2020
OS/Arch: linux/amd64
Context: default
Experimental: true
Server: Docker Engine - Community
Engine:
Version: 20.10.1
API version: 1.41 (minimum version 1.12)
Go version: go1.13.15
Git commit: f001486
Built: Tue Dec 15 04:32:52 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.5.0-docker)
Server:
Containers: 2
Running: 1
Paused: 0
Stopped: 1
Images: 5
Server Version: 20.10.1
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.runc.v2 io.containerd.runtime.v1.linux runc
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-58-generic
Operating System: Ubuntu 20.04.1 LTS
OSType: linux
Architecture: x86_64
CPUs: 1
Total Memory: 981.2MiB
Name: hk.zju.co
ID: EZ3R:GFZG:PCIO:CEYW:Z3P5:MIND:EDKS:2VDJ:HVPF:SAWD:BKQY:OP2H
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: true
WARNING: No swap limit support
WARNING: No blkio weight support
WARNING: No blkio weight_device support
Additional environment details (AWS, VirtualBox, physical, etc.):
N/A
Description
After upgrading docker-ce to 20.10.x, reboot/shutdown the machine hangs 90s due to containerd-shim.
Steps to reproduce the issue:
docker run -d k8s.gcr.io/pausesudo rebootDescribe the results you received:
The shutdown/reboot process stuck for 90s, due to containerd-shim.
Describe the results you expected:
containerd-shim should not interfere with shutdown/reboot process.
Additional information you deem important (e.g. issue happens only occasionally):
Since #41210, the default runtime is runc v2. The old runc v1 runtime does not have this issue. Tested with the following commands.
Output of
docker version:Output of
docker info:Additional environment details (AWS, VirtualBox, physical, etc.):
N/A