moby: docker daemon -s overlayfs, Failed to connect to containerd,
Output of docker version
:
ld8529:~ # docker version
Client:
Version: 1.11.1
API version: 1.23
Go version: go1.6.1
Git commit: 9e83765
Built:
OS/Arch: linux/amd64
Server: Version: 1.11.1 API version: 1.23 Go version: go1.6.1 Git commit: 9e83765 Built: OS/Arch: linux/amd64
(paste your output here)
ld8529:~ # docker daemon -s overlayfs FATA[0000] Failed to connect to containerd. Please make sure containerd is installed in your PATH or you have specificed the correct address. Got error: exec: “docker-containerd”: executable file not found in $PATH
Output of docker info
:
ld8529:~ # docker info
Containers: 0
Running: 0
Paused: 0
Stopped: 0
Images: 0
Server Version: 1.11.1
Storage Driver: devicemapper
Pool Name: docker-254:6-2016-pool
Pool Blocksize: 65.54 kB
Base Device Size: 10.74 GB
Backing Filesystem: xfs
Data file: /dev/loop2
Metadata file: /dev/loop3
Data Space Used: 11.73 MB
Data Space Total: 107.4 GB
Data Space Available: 1.443 GB
Metadata Space Used: 581.6 kB
Metadata Space Total: 2.147 GB
Metadata Space Available: 1.443 GB
Udev Sync Supported: true
Deferred Removal Enabled: false
Deferred Deletion Enabled: false
Deferred Deleted Device Count: 0
Data loop file: /var/lib/docker/devicemapper/devicemapper/data
WARNING: Usage of loopback devices is strongly discouraged for production use. Either use --storage-opt dm.thinpooldev
or use --storage-opt dm.no_warn_on_loop_devices=true
to suppress this warning.
Metadata loop file: /var/lib/docker/devicemapper/devicemapper/metadata
Library Version: 1.03.01 (2016-01-25)
Logging Driver: json-file
Cgroup Driver: cgroupfs
Plugins:
Volume: local
Network: host bridge null
Kernel Version: 3.12.51-52.39-default
Operating System: SUSE Linux Enterprise Server 12
OSType: linux
Architecture: x86_64
CPUs: 64
Total Memory: 504.9 GiB
Name: ld8529
ID: FFSR:FEUL:IY2F:QPCA:6HPD:UBCH:FFVL:LNCT:EMWL:XESU:45LL:MOSP
Docker Root Dir: /var/lib/docker
Debug mode (client): false
Debug mode (server): false
Registry: https://index.docker.io/v1/
WARNING: No swap limit support
WARNING: No kernel memory limit support
(paste your output here)
ld8529:~ # docker info
Containers: 0
Running: 0
Paused: 0
Stopped: 0
Images: 0
Server Version: 1.11.1
Storage Driver: devicemapper
Pool Name: docker-254:6-2016-pool
Pool Blocksize: 65.54 kB
Base Device Size: 10.74 GB
Backing Filesystem: xfs
Data file: /dev/loop2
Metadata file: /dev/loop3
Data Space Used: 11.73 MB
Data Space Total: 107.4 GB
Data Space Available: 1.443 GB
Metadata Space Used: 581.6 kB
Metadata Space Total: 2.147 GB
Metadata Space Available: 1.443 GB
Udev Sync Supported: true
Deferred Removal Enabled: false
Deferred Deletion Enabled: false
Deferred Deleted Device Count: 0
Data loop file: /var/lib/docker/devicemapper/devicemapper/data
WARNING: Usage of loopback devices is strongly discouraged for production use. Either use --storage-opt dm.thinpooldev
or use --storage-opt dm.no_warn_on_loop_devices=true
to suppress this warning.
Metadata loop file: /var/lib/docker/devicemapper/devicemapper/metadata
Library Version: 1.03.01 (2016-01-25)
Logging Driver: json-file
Cgroup Driver: cgroupfs
Plugins:
Volume: local
Network: host bridge null
Kernel Version: 3.12.51-52.39-default
Operating System: SUSE Linux Enterprise Server 12
OSType: linux
Architecture: x86_64
CPUs: 64
Total Memory: 504.9 GiB
Name: ld8529
ID: FFSR:FEUL:IY2F:QPCA:6HPD:UBCH:FFVL:LNCT:EMWL:XESU:45LL:MOSP
Docker Root Dir: /var/lib/docker
Debug mode (client): false
Debug mode (server): false
Registry: https://index.docker.io/v1/
WARNING: No swap limit support
WARNING: No kernel memory limit support
Additional environment details (AWS, VirtualBox, physical, etc.):
suse 12.1 enterprise
Steps to reproduce the issue:
- systemctl stop docker
- docker daemon -s overlayfs
Describe the results you received: ld8529:~ # echo $PATH /sbin:/usr/sbin:/usr/local/sbin:/root/bin:/usr/local/bin:/usr/bin:/bin:/usr/bin/X11:/usr/games:/opt/MegaRAID/MegaCli:/opt/MegaRAID/storcli:/root/bin ld8529:~ # whereis containerd containerd: /usr/sbin/containerd
ld8529:~ # docker daemon -s overlayfs FATA[0000] Failed to connect to containerd. Please make sure containerd is installed in your PATH or you have specificed the correct address. Got error: exec: “docker-containerd”: executable file not found in $PATH
Describe the results you expected: docker deamon run ok
Additional information you deem important (e.g. issue happens only occasionally):
About this issue
- Original URL
- State: closed
- Created 8 years ago
- Comments: 24 (14 by maintainers)
@hanae2e How did you install docker? Docker is now comprised for 4 binaries,
docker
,docker-contianerd
,docker-runc
, anddocker-containerd-shim