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

[1.11.1] Docker bootstrap: Cannot start a container because of oci runtime error. #22684

Closed
zreigz opened this Issue May 12, 2016 · 20 comments

Comments

Projects
None yet
5 participants
@zreigz
Contributor

zreigz commented May 12, 2016

Output of docker version:

Docker version 1.11.1, build 5604cbe

Output of docker info:

Containers: 0
 Running: 0
 Paused: 0
 Stopped: 0
Images: 1
Server Version: 1.11.1
Storage Driver: devicemapper
 Pool Name: docker-253:0-394509-pool
 Pool Blocksize: 65.54 kB
 Base Device Size: 10.74 GB
 Backing Filesystem: xfs
 Data file: /dev/loop0
 Metadata file: /dev/loop1
 Data Space Used: 19.07 MB
 Data Space Total: 107.4 GB
 Data Space Available: 38.76 GB
 Metadata Space Used: 589.8 kB
 Metadata Space Total: 2.147 GB
 Metadata Space Available: 2.147 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.02.107-RHEL7 (2015-12-01)
Logging Driver: json-file
Cgroup Driver: cgroupfs
Plugins: 
 Volume: local
 Network: bridge null host
Kernel Version: 3.10.0-327.13.1.el7.x86_64
Operating System: CentOS Linux 7 (Core)
OSType: linux
Architecture: x86_64
CPUs: 2
Total Memory: 1.797 GiB
Name: localhost.localdomain
ID: E3X2:DQ6O:DVIO:2NPO:XFY7:6P65:SQG2:TXLM:EERQ:GFSO:NUWT:JF3S
Docker Root Dir: /var/lib/docker
Debug mode (client): false
Debug mode (server): false
Registry: https://index.docker.io/v1/
WARNING: bridge-nf-call-iptables is disabled
WARNING: bridge-nf-call-ip6tables is disabled

Additional environment details (AWS, VirtualBox, physical, etc.): Vagrant centos/7 box

Steps to reproduce the issue:

  1. Start docker as a bootstrap service in one console:
docker daemon \
        -H unix:///var/run/docker-bootstrap.sock \
        -p /var/run/docker-bootstrap.pid \
        --iptables=false \
        --ip-masq=false \
        --bridge=none \
        --graph=/var/lib/docker-bootstrap --debug
  1. Start container in second console:
docker -H unix:///var/run/docker-bootstrap.sock run -it --rm busybox sh

Describe the results you received:

Status: Downloaded newer image for busybox:latest
docker: Error response from daemon: rpc error: code = 2 desc = "oci runtime error: rootfs (\"/var/lib/docker-bootstrap/devicemapper/mnt/8c8cc49901da0ddbdd24298a7b294dc7a516a9c72d05055fd882964101f46897/rootfs\") does not exist".

Excerpts from docker daemon logs with debugs enabled

DEBU[0044] Calling POST /v1.23/containers/create        
DEBU[0044] form data: {"AttachStderr":true,"AttachStdin":true,"AttachStdout":true,"Cmd":["sh"],"Domainname":"","Entrypoint":null,"Env":[],"HostConfig":{"AutoRemove":false,"Binds":null,"BlkioBps":0,"BlkioDeviceReadBps":null,"BlkioDeviceReadIOps":null,"BlkioDeviceWriteBps":null,"BlkioDeviceWriteIOps":null,"BlkioIOps":0,"BlkioWeight":0,"BlkioWeightDevice":null,"CapAdd":null,"CapDrop":null,"Cgroup":"","CgroupParent":"","ConsoleSize":[0,0],"ContainerIDFile":"","CpuCount":0,"CpuPercent":0,"CpuPeriod":0,"CpuQuota":0,"CpuShares":0,"CpusetCpus":"","CpusetMems":"","Devices":[],"DiskQuota":0,"Dns":[],"DnsOptions":[],"DnsSearch":[],"ExtraHosts":null,"GroupAdd":null,"IpcMode":"","Isolation":"","KernelMemory":0,"Links":null,"LogConfig":{"Config":{},"Type":""},"Memory":0,"MemoryReservation":0,"MemorySwap":0,"MemorySwappiness":-1,"NetworkMode":"default","OomKillDisable":false,"OomScoreAdj":0,"PidMode":"","PidsLimit":0,"PortBindings":{},"Privileged":false,"PublishAllPorts":false,"ReadonlyRootfs":false,"RestartPolicy":{"MaximumRetryCount":0,"Name":"no"},"SandboxSize":0,"SecurityOpt":null,"ShmSize":0,"StorageOpt":null,"UTSMode":"","Ulimits":null,"UsernsMode":"","VolumeDriver":"","VolumesFrom":null},"Hostname":"","Image":"busybox","Labels":{},"NetworkingConfig":{"EndpointsConfig":{}},"OnBuild":null,"OpenStdin":true,"StdinOnce":true,"Tty":true,"User":"","Volumes":{},"WorkingDir":""} 
DEBU[0044] devmapper: AddDevice(hash=35599f75db637c6ccb495551f4fbec98e105bf273d348d137d506d38527d4032-init basehash=a88c80f3742d46b2f22e9c41acb7d4ca83c59054bbe8efdd7f196b7d5f8a7ca3) 
DEBU[0044] devmapper: registerDevice(17, 35599f75db637c6ccb495551f4fbec98e105bf273d348d137d506d38527d4032-init) 
DEBU[0044] devmapper: AddDevice(hash=35599f75db637c6ccb495551f4fbec98e105bf273d348d137d506d38527d4032-init basehash=a88c80f3742d46b2f22e9c41acb7d4ca83c59054bbe8efdd7f196b7d5f8a7ca3) END 
DEBU[0044] devmapper: activateDeviceIfNeeded(35599f75db637c6ccb495551f4fbec98e105bf273d348d137d506d38527d4032-init) 
DEBU[0044] devmapper: UnmountDevice(hash=35599f75db637c6ccb495551f4fbec98e105bf273d348d137d506d38527d4032-init) 
DEBU[0044] devmapper: Unmount(/var/lib/docker-bootstrap/devicemapper/mnt/35599f75db637c6ccb495551f4fbec98e105bf273d348d137d506d38527d4032-init) 
DEBU[0045] devmapper: Unmount done                      
DEBU[0045] devmapper: deactivateDevice(35599f75db637c6ccb495551f4fbec98e105bf273d348d137d506d38527d4032-init) 
DEBU[0045] devmapper: removeDevice START(docker-253:0-394747-35599f75db637c6ccb495551f4fbec98e105bf273d348d137d506d38527d4032-init) 
DEBU[0045] devmapper: removeDevice END(docker-253:0-394747-35599f75db637c6ccb495551f4fbec98e105bf273d348d137d506d38527d4032-init) 
DEBU[0045] devmapper: deactivateDevice END(35599f75db637c6ccb495551f4fbec98e105bf273d348d137d506d38527d4032-init) 
DEBU[0045] devmapper: UnmountDevice(hash=35599f75db637c6ccb495551f4fbec98e105bf273d348d137d506d38527d4032-init) END 
DEBU[0045] devmapper: AddDevice(hash=35599f75db637c6ccb495551f4fbec98e105bf273d348d137d506d38527d4032 basehash=35599f75db637c6ccb495551f4fbec98e105bf273d348d137d506d38527d4032-init) 
DEBU[0045] devmapper: registerDevice(18, 35599f75db637c6ccb495551f4fbec98e105bf273d348d137d506d38527d4032) 
DEBU[0045] devmapper: AddDevice(hash=35599f75db637c6ccb495551f4fbec98e105bf273d348d137d506d38527d4032 basehash=35599f75db637c6ccb495551f4fbec98e105bf273d348d137d506d38527d4032-init) END 
DEBU[0045] devmapper: activateDeviceIfNeeded(35599f75db637c6ccb495551f4fbec98e105bf273d348d137d506d38527d4032) 
DEBU[0045] container mounted via layerStore: /var/lib/docker-bootstrap/devicemapper/mnt/35599f75db637c6ccb495551f4fbec98e105bf273d348d137d506d38527d4032/rootfs 
DEBU[0045] devmapper: UnmountDevice(hash=35599f75db637c6ccb495551f4fbec98e105bf273d348d137d506d38527d4032) 
DEBU[0045] devmapper: Unmount(/var/lib/docker-bootstrap/devicemapper/mnt/35599f75db637c6ccb495551f4fbec98e105bf273d348d137d506d38527d4032) 
DEBU[0045] devmapper: Unmount done                      
DEBU[0045] devmapper: deactivateDevice(35599f75db637c6ccb495551f4fbec98e105bf273d348d137d506d38527d4032) 
DEBU[0045] devmapper: removeDevice START(docker-253:0-394747-35599f75db637c6ccb495551f4fbec98e105bf273d348d137d506d38527d4032) 
DEBU[0045] devmapper: removeDevice END(docker-253:0-394747-35599f75db637c6ccb495551f4fbec98e105bf273d348d137d506d38527d4032) 
DEBU[0045] devmapper: deactivateDevice END(35599f75db637c6ccb495551f4fbec98e105bf273d348d137d506d38527d4032) 
DEBU[0045] devmapper: UnmountDevice(hash=35599f75db637c6ccb495551f4fbec98e105bf273d348d137d506d38527d4032) END 
DEBU[0045] Calling POST /v1.23/containers/f5ff62db4ba13a71321d8d5ea77e7c5990617de72214c417b441a63d1651c16b/attach?stderr=1&stdin=1&stdout=1&stream=1 
DEBU[0045] attach: stdin: begin                         
DEBU[0045] attach: stdout: begin                        
DEBU[0045] attach: stderr: begin                        
DEBU[0045] Calling POST /v1.23/containers/f5ff62db4ba13a71321d8d5ea77e7c5990617de72214c417b441a63d1651c16b/start 
DEBU[0045] devmapper: activateDeviceIfNeeded(35599f75db637c6ccb495551f4fbec98e105bf273d348d137d506d38527d4032) 
DEBU[0045] container mounted via layerStore: /var/lib/docker-bootstrap/devicemapper/mnt/35599f75db637c6ccb495551f4fbec98e105bf273d348d137d506d38527d4032/rootfs 
DEBU[0045] devmapper: UnmountDevice(hash=35599f75db637c6ccb495551f4fbec98e105bf273d348d137d506d38527d4032) 
DEBU[0045] devmapper: Unmount(/var/lib/docker-bootstrap/devicemapper/mnt/35599f75db637c6ccb495551f4fbec98e105bf273d348d137d506d38527d4032) 
DEBU[0045] attach: stdout: end                          
DEBU[0045] attach: stdin: end                           
DEBU[0045] attach: stderr: end                          
DEBU[0045] devmapper: Unmount done                      
DEBU[0045] devmapper: deactivateDevice(35599f75db637c6ccb495551f4fbec98e105bf273d348d137d506d38527d4032) 
DEBU[0045] devmapper: removeDevice START(docker-253:0-394747-35599f75db637c6ccb495551f4fbec98e105bf273d348d137d506d38527d4032) 
DEBU[0045] devmapper: removeDevice END(docker-253:0-394747-35599f75db637c6ccb495551f4fbec98e105bf273d348d137d506d38527d4032) 
DEBU[0045] devmapper: deactivateDevice END(35599f75db637c6ccb495551f4fbec98e105bf273d348d137d506d38527d4032) 
DEBU[0045] devmapper: UnmountDevice(hash=35599f75db637c6ccb495551f4fbec98e105bf273d348d137d506d38527d4032) END 
ERRO[0045] Handler for POST /v1.23/containers/f5ff62db4ba13a71321d8d5ea77e7c5990617de72214c417b441a63d1651c16b/start returned error: rpc error: code = 2 desc = "oci runtime error: rootfs (\"/var/lib/docker-bootstrap/devicemapper/mnt/35599f75db637c6ccb495551f4fbec98e105bf273d348d137d506d38527d4032/rootfs\") does not exist" 
DEBU[0045] Calling DELETE /v1.23/containers/f5ff62db4ba13a71321d8d5ea77e7c5990617de72214c417b441a63d1651c16b?v=1 
DEBU[0045] devmapper: DeleteDevice(hash=35599f75db637c6ccb495551f4fbec98e105bf273d348d137d506d38527d4032 syncDelete=false) START 
DEBU[0045] devmapper: issueDiscard(device: 35599f75db637c6ccb495551f4fbec98e105bf273d348d137d506d38527d4032). START 
DEBU[0045] devmapper: activateDeviceIfNeeded(35599f75db637c6ccb495551f4fbec98e105bf273d348d137d506d38527d4032) 
DEBU[0045] devmapper: issueDiscard(device: 35599f75db637c6ccb495551f4fbec98e105bf273d348d137d506d38527d4032). END 
DEBU[0045] devmapper: deactivateDevice(35599f75db637c6ccb495551f4fbec98e105bf273d348d137d506d38527d4032) 
DEBU[0045] devmapper: removeDevice START(docker-253:0-394747-35599f75db637c6ccb495551f4fbec98e105bf273d348d137d506d38527d4032) 
DEBU[0045] devmapper: removeDevice END(docker-253:0-394747-35599f75db637c6ccb495551f4fbec98e105bf273d348d137d506d38527d4032) 
DEBU[0045] devmapper: deactivateDevice END(35599f75db637c6ccb495551f4fbec98e105bf273d348d137d506d38527d4032) 
DEBU[0045] devmapper: unregisterDevice(18, 35599f75db637c6ccb495551f4fbec98e105bf273d348d137d506d38527d4032) 
DEBU[0045] devmapper: DeleteDevice(hash=35599f75db637c6ccb495551f4fbec98e105bf273d348d137d506d38527d4032 syncDelete=false) END 
DEBU[0045] devmapper: DeleteDevice(hash=35599f75db637c6ccb495551f4fbec98e105bf273d348d137d506d38527d4032-init syncDelete=false) START 
DEBU[0045] devmapper: issueDiscard(device: 35599f75db637c6ccb495551f4fbec98e105bf273d348d137d506d38527d4032-init). START 
DEBU[0045] devmapper: activateDeviceIfNeeded(35599f75db637c6ccb495551f4fbec98e105bf273d348d137d506d38527d4032-init) 
DEBU[0045] devmapper: issueDiscard(device: 35599f75db637c6ccb495551f4fbec98e105bf273d348d137d506d38527d4032-init). END 
DEBU[0045] devmapper: deactivateDevice(35599f75db637c6ccb495551f4fbec98e105bf273d348d137d506d38527d4032-init) 
DEBU[0045] devmapper: removeDevice START(docker-253:0-394747-35599f75db637c6ccb495551f4fbec98e105bf273d348d137d506d38527d4032-init) 
DEBU[0045] devmapper: removeDevice END(docker-253:0-394747-35599f75db637c6ccb495551f4fbec98e105bf273d348d137d506d38527d4032-init) 
DEBU[0045] devmapper: deactivateDevice END(35599f75db637c6ccb495551f4fbec98e105bf273d348d137d506d38527d4032-init) 
DEBU[0045] devmapper: unregisterDevice(17, 35599f75db637c6ccb495551f4fbec98e105bf273d348d137d506d38527d4032-init) 
DEBU[0045] devmapper: DeleteDevice(hash=35599f75db637c6ccb495551f4fbec98e105bf273d348d137d506d38527d4032-init syncDelete=false) END 
DEBU[0045] Closing buffered stdin pipe         
@zreigz

This comment has been minimized.

Contributor

zreigz commented May 12, 2016

@thaJeztah

This comment has been minimized.

Member

thaJeztah commented May 12, 2016

Seems to work on Ubuntu, but I can try reproducing on a CentOS host

docker -H unix:///var/run/docker-bootstrap.sock info
Containers: 0
 Running: 0
 Paused: 0
 Stopped: 0
Images: 1
Server Version: 1.11.1
Storage Driver: aufs
 Root Dir: /var/lib/docker-bootstrap/aufs
 Backing Filesystem: extfs
 Dirs: 2
 Dirperm1 Supported: true
Logging Driver: json-file
Cgroup Driver: cgroupfs
Plugins:
 Volume: local
 Network: null host
Kernel Version: 4.2.0-27-generic
Operating System: Ubuntu 15.10
OSType: linux
Architecture: x86_64
CPUs: 2
Total Memory: 1.954 GiB
Name: ubuntu-2gb-ams3-01
ID: Y5HS:2JVU:MNOJ:Y7KE:RDFO:C7OJ:TZIS:77EA:LPFN:VBCV:YM6G:NCYQ
Docker Root Dir: /var/lib/docker-bootstrap
Debug mode (client): false
Debug mode (server): true
 File Descriptors: 13
 Goroutines: 29
 System Time: 2016-05-12T08:39:38.213693283-04:00
 EventsListeners: 0
Registry: https://index.docker.io/v1/
WARNING: No swap limit support
@thaJeztah

This comment has been minimized.

Member

thaJeztah commented May 12, 2016

Same on CentOS 7.2

docker -H unix:///var/run/docker-bootstrap.sock info
Containers: 0
 Running: 0
 Paused: 0
 Stopped: 0
Images: 1
Server Version: 1.11.1
Storage Driver: devicemapper
 Pool Name: docker-253:1-262181-pool
 Pool Blocksize: 65.54 kB
 Base Device Size: 10.74 GB
 Backing Filesystem: xfs
 Data file: /dev/loop0
 Metadata file: /dev/loop1
 Data Space Used: 19.07 MB
 Data Space Total: 107.4 GB
 Data Space Available: 40.63 GB
 Metadata Space Used: 589.8 kB
 Metadata Space Total: 2.147 GB
 Metadata Space Available: 2.147 GB
 Udev Sync Supported: true
 Deferred Removal Enabled: false
 Deferred Deletion Enabled: false
 Deferred Deleted Device Count: 0
 Data loop file: /var/lib/docker-bootstrap/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-bootstrap/devicemapper/devicemapper/metadata
 Library Version: 1.02.107-RHEL7 (2015-12-01)
Logging Driver: json-file
Cgroup Driver: cgroupfs
Plugins:
 Volume: local
 Network: null host
Kernel Version: 3.10.0-327.10.1.el7.x86_64
Operating System: CentOS Linux 7 (Core)
OSType: linux
Architecture: x86_64
CPUs: 2
Total Memory: 1.954 GiB
Name: centos-2gb-ams3-01
ID: VTDV:LIY6:YXSK:S5DE:4CMV:N6QK:MKTW:4XCW:57XB:KRR7:MSOE:LXHP
Docker Root Dir: /var/lib/docker-bootstrap
Debug mode (client): false
Debug mode (server): true
 File Descriptors: 14
 Goroutines: 29
 System Time: 2016-05-12T09:09:36.849913681-04:00
 EventsListeners: 0
Registry: https://index.docker.io/v1/
WARNING: bridge-nf-call-iptables is disabled
WARNING: bridge-nf-call-ip6tables is disabled
@justincormack

This comment has been minimized.

Contributor

justincormack commented May 12, 2016

Are you running this in addition to another docker instance?

@zreigz

This comment has been minimized.

Contributor

zreigz commented May 12, 2016

I made some research about this problem and it exists only on Vagrant with centos7 box.
I have very simple scenario:

Those steps are done in this project: https://github.com/zreigz/docker-vagrant

When vagrant provisioning is done then you should:

  • vagrant ssh to get to the VM
  • In VM
[vagrant@vagrantbox ~]$ sudo su
[root@vagrantbox vagrant]# docker daemon \
        -H unix:///var/run/docker-bootstrap.sock \
        -p /var/run/docker-bootstrap.pid \
        --iptables=false \
        --ip-masq=false \
        --bridge=none \
        --graph=/var/lib/docker-bootstrap &


[root@vagrantbox vagrant]# docker -H unix:///var/run/docker-bootstrap.sock run -it --rm busybox sh

Then you see the error.

When I made downgrade to docker 1.10.3 then everything works fine

@thaJeztah

This comment has been minimized.

Member

thaJeztah commented May 12, 2016

Can you update your docker.unit to match the https://github.com/docker/docker/blob/master/contrib/init/systemd/docker.service unit-file? I see various settings missing (e.g. MountFlags=slave, Delegate=yes)

@justincormack

This comment has been minimized.

Contributor

justincormack commented May 12, 2016

It might be an selinux issue then, denying access to that part of /var -
can you check the audit log?
On 12 May 2016 6:57 p.m., "Lukasz Zajaczkowski" notifications@github.com
wrote:

I made some research about this problem and it exists only on Vagrant with
centos7 box.
I have very simple scenario:

Those steps are done in this project:
https://github.com/zreigz/docker-vagrant

When vagrant provisioning is done then you should:

  • vagrant ssh to get to the VM
  • In VM

[vagrant@vagrantbox ~]$ sudo su
[root@vagrantbox vagrant]# docker daemon
-H unix:///var/run/docker-bootstrap.sock
-p /var/run/docker-bootstrap.pid
--iptables=false
--ip-masq=false
--bridge=none
--graph=/var/lib/docker-bootstrap &

[root@vagrantbox vagrant]# docker -H unix:///var/run/docker-bootstrap.sock run -it --rm busybox sh

Then you see the error.

When I made downgrade to docker 1.10.3 then everything works fine


You are receiving this because you commented.
Reply to this email directly or view it on GitHub
#22684 (comment)

@zreigz

This comment has been minimized.

Contributor

zreigz commented May 12, 2016

@thaJeztah I think the docker service looks similar. This is from Vagrant instance:

cat /usr/lib/systemd/system/docker.service
[Unit]
Description=Docker Application Container Engine
Documentation=https://docs.docker.com
After=network.target docker.socket
Requires=docker.socket

[Service]
Type=notify
# the default is not to use systemd for cgroups because the delegate issues still
# exists and systemd currently does not support the cgroup feature set required
# for containers run by docker
ExecStart=/usr/bin/docker daemon -H fd://
MountFlags=slave
LimitNOFILE=1048576
LimitNPROC=1048576
LimitCORE=infinity
TimeoutStartSec=0
# set delegate yes so that systemd does not reset the cgroups of docker containers
Delegate=yes

[Install]
WantedBy=multi-user.target

I also tried with MountFlags=shared but without success

@justincormack how can I check audit log?

@zreigz

This comment has been minimized.

Contributor

zreigz commented May 12, 2016

I just made downgrade to:
Docker version 1.11.0, build 4dc5990 and works fine, so the problem appeared in 1.11.1
For 1.10.3 I also didn't notice any problems

@thaJeztah

This comment has been minimized.

Member

thaJeztah commented May 12, 2016

@zreigz thanks! I saw the "template" in your repository, and thought that was used

@justincormack

This comment has been minimized.

Contributor

justincormack commented May 12, 2016

@zreigz should be in /var/log/audit/audit.log

@zreigz

This comment has been minimized.

Contributor

zreigz commented May 13, 2016

This is audit.log. I can not see any suspicious entries.
audit.log.zip

@f-higashi

This comment has been minimized.

f-higashi commented May 13, 2016

When execute systemctl stop docker and start docker-bootstrap daemon, it is success.
Both docker daemon use same socket of docker-containerd.

It seems to be related to #22256.

@zreigz

This comment has been minimized.

Contributor

zreigz commented May 13, 2016

OK I found solution. Similar problem is described here: kubernetes/kubernetes#24654

I've added --exec-root=/var/lib/docker-bootstrap
and it looks like

docker daemon \
        -H unix:///var/run/docker-bootstrap.sock \
        -p /var/run/docker-bootstrap.pid \
        --iptables=false \
        --ip-masq=false \
        --bridge=none \
        --graph=/var/lib/docker-bootstrap \
       --exec-root=/var/lib/docker-bootstrap

Problem fixed

@thaJeztah

This comment has been minimized.

Member

thaJeztah commented May 13, 2016

@zreigz hm, I wonder if that should be --exec-root=/var/run/docker-bootstrap (not /var/lib..)

Perhaps this should be documented better, because it looks like we're not really documenting the --exec-root option. Would you be interested in contributing changes for that? Should probably go in this document; https://github.com/docker/docker/blob/master/docs/reference/commandline/dockerd.md

(and the associated man page; https://github.com/docker/docker/blob/master/man/dockerd.8.md)

@justincormack

This comment has been minimized.

Contributor

justincormack commented May 13, 2016

Yes I think improved docs would help as it has changed quite a bit since containerd and there seem to be more people interested in running multiple dockers recently.

@zreigz

This comment has been minimized.

Contributor

zreigz commented May 13, 2016

@thaJeztah Yes you are right. The --exec-root=/var/run/docker-bootstrap is better.
Sure I can improve documentation

@thaJeztah

This comment has been minimized.

Member

thaJeztah commented May 13, 2016

Perhaps a section "running multiple daemons" or something similar (explaining the options to configure, and a warning that they should never share the same graph-dir 😇 )

@icecrime

This comment has been minimized.

Contributor

icecrime commented Aug 30, 2016

@zreigz Hi! Are you ok closing this issue or do you think there's additional work to be done to fully resolve it? Thanks.

@zreigz

This comment has been minimized.

Contributor

zreigz commented Aug 31, 2016

Yes I can close it

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment