moby: docker restart failed after machine reboot
Description
Steps to reproduce the issue:
machine reboot
then start docker
dockerd -g /data/docker -H unix:///var/run/docker.sock -b none --live-restore -s aufs --iptables=False
and
FATA[0000] open /var/run/docker/libcontainerd/containerd/10cf98fe5158d10b4c337017d7a6cb67166ac1ea3d1aa2733a8b27fa6c235a07/state.json: no such file or directory
I have to rm -rf /var/run/docker and start docker again,and all is fine again Additional information you deem important (e.g. issue happens only occasionally): always Output of docker version:
Client:
Version: 1.12.2
API version: 1.24
Go version: go1.6.3
Git commit: bb80604
Built: Tue Oct 11 17:00:50 2016
OS/Arch: linux/amd64
Server:
Version: 1.12.2
API version: 1.24
Go version: go1.6.3
Git commit: bb80604
Built: Tue Oct 11 17:00:50 2016
OS/Arch: linux/amd64
Output of docker info:
Containers: 12
Running: 11
Paused: 0
Stopped: 1
Images: 10
Server Version: 1.12.2
Storage Driver: aufs
Root Dir: /data/docker/aufs
Backing Filesystem: xfs
Dirs: 163
Dirperm1 Supported: true
Logging Driver: json-file
Cgroup Driver: cgroupfs
Plugins:
Volume: local
Network: host null overlay
Swarm: inactive
Runtimes: runc
Default Runtime: runc
Security Options:
Kernel Version: 3.10.104.xxxxxx
Operating System: <unknown>
OSType: linux
Architecture: x86_64
CPUs: 48
Total Memory: 125.3 GiB
Name: xxxxxxxxxxxxxxxxx
ID: VTSE:3AJP:MWYG:XSRO:VLHA:7RUN:S5KP:SDB4:HVDP:5HT3:24XC:VW52
Docker Root Dir: /data/docker
Debug Mode (client): false
Debug Mode (server): false
Registry: https://index.docker.io/v1/
Insecure Registries:
127.0.0.0/8
Additional environment details (AWS, VirtualBox, physical, etc.):
centos 6 with 3.10.x kernel version.
About this issue
- Original URL
- State: closed
- Created 8 years ago
- Comments: 16 (14 by maintainers)
The fix was merged into docker in https://github.com/moby/moby/pull/31662, which is part of the 17.03.1 release, so let me close this issue
@sandyskies it seems a
state.json
is missing for the1915b785d4b33931f665c6510f6cf8399f58f5d41166f2400264b6fdc5c1ca0f
container somehow.Deleting that directory should allow
containerd
to keep going (i.e.rm -rf /var/run/docker/libcontainerd/containerd/1915b785d4b33931f665c6510f6cf8399f58f5d41166f2400264b6fdc5c1ca0f/
).Although, if that container is still running or docker hasn’t seen it die, it won’t be able to be acted upon afterwards.