October 30, 20205 yr Hello, I am having some issues while trying to run docker inside a Debian VM machine. I need to move the docker data to an unRAID shared volume to take advantage of unRAID capabilities, so I did the following: 1. Stop docker and create the mounting point: root@dappnode:~# systemctl stop docker root@dappnode:~# mkdir /var/lib/mountedDocker root@dappnode:~# cp /var/lib/docker/* /var/lib/mountedDocker/ 2. Edit the /etc/fstab to add the share volume: unraid /var/lib/mountedDocker/ 9p msize=262144,trans=virtio,version=9p2000.L,_netdev,rw 0 0 3. Edit /etc/docker/daemon.json as follows: { "data-root": "/var/lib/mountedDocker" } 4. Mount unraid volume and start docker service: root@dappnode:~# mount unraid root@dappnode:~# systemctl start docker Job for docker.service failed because the control process exited with error code. See "systemctl status docker.service" and "journalctl -xe" for details. root@dappnode:~# systemctl status docker.service ● docker.service - Docker Application Container Engine Loaded: loaded (/lib/systemd/system/docker.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Fri 2020-10-30 09:02:43 CET; 1min 20s ago TriggeredBy: ● docker.socket Docs: https://docs.docker.com Process: 3980 ExecStart=/usr/bin/dockerd -H fd:// --containerd=/run/containerd/containerd.sock (code=exited, status=1/FAILURE) Main PID: 3980 (code=exited, status=1/FAILURE) oct 30 09:02:43 dappnode systemd[1]: Stopped Docker Application Container Engine. oct 30 09:02:43 dappnode systemd[1]: docker.service: Start request repeated too quickly. oct 30 09:02:43 dappnode systemd[1]: docker.service: Failed with result 'exit-code'. oct 30 09:02:43 dappnode systemd[1]: Failed to start Docker Application Container Engine. oct 30 09:03:12 dappnode systemd[1]: docker.service: Start request repeated too quickly. oct 30 09:03:12 dappnode systemd[1]: docker.service: Failed with result 'exit-code'. oct 30 09:03:12 dappnode systemd[1]: Failed to start Docker Application Container Engine. oct 30 09:03:21 dappnode systemd[1]: docker.service: Start request repeated too quickly. oct 30 09:03:21 dappnode systemd[1]: docker.service: Failed with result 'exit-code'. oct 30 09:03:21 dappnode systemd[1]: Failed to start Docker Application Container Engine. What I am doing wrong? Thanks!
October 31, 20205 yr Author To ensure that the mount is performed before docker service init I am adding the following line to /etc/systemd/system/multi-user.target.wants/docker.service in the service section RequiresMountsFor=unraid But I get the following: root@dappnode:~# systemctl start docker Job for docker.service failed because the control process exited with error code. See "systemctl status docker.service" and "journalctl -xe" for details. root@dappnode:~# journalctl -xe ░░ ░░ A start job for unit docker.socket has finished successfully. ░░ ░░ The job identifier is 2309. oct 31 14:44:12 dappnode systemd[1]: Starting Docker Application Container Engine... ░░ Subject: A start job for unit docker.service has begun execution ░░ Defined-By: systemd ░░ Support: https://www.debian.org/support ░░ ░░ A start job for unit docker.service has begun execution. ░░ ░░ The job identifier is 2219. oct 31 14:44:12 dappnode dockerd[8204]: time="2020-10-31T14:44:12.213669845+01:00" level=info msg="Starting up" oct 31 14:44:12 dappnode dockerd[8204]: time="2020-10-31T14:44:12.230913760+01:00" level=info msg="parsed scheme: \"unix\"" module=grpc oct 31 14:44:12 dappnode dockerd[8204]: time="2020-10-31T14:44:12.230951468+01:00" level=info msg="scheme \"unix\" not registered, fallback to default scheme" module=grpc oct 31 14:44:12 dappnode dockerd[8204]: time="2020-10-31T14:44:12.230973392+01:00" level=info msg="ccResolverWrapper: sending update to cc: {[{unix:///run/containerd/containerd.sock 0 <nil>}] <nil>}" mo> oct 31 14:44:12 dappnode dockerd[8204]: time="2020-10-31T14:44:12.230985844+01:00" level=info msg="ClientConn switching balancer to \"pick_first\"" module=grpc oct 31 14:44:12 dappnode dockerd[8204]: time="2020-10-31T14:44:12.234123279+01:00" level=info msg="parsed scheme: \"unix\"" module=grpc oct 31 14:44:12 dappnode dockerd[8204]: time="2020-10-31T14:44:12.234152959+01:00" level=info msg="scheme \"unix\" not registered, fallback to default scheme" module=grpc oct 31 14:44:12 dappnode dockerd[8204]: time="2020-10-31T14:44:12.234169882+01:00" level=info msg="ccResolverWrapper: sending update to cc: {[{unix:///run/containerd/containerd.sock 0 <nil>}] <nil>}" mo> oct 31 14:44:12 dappnode dockerd[8204]: time="2020-10-31T14:44:12.234181312+01:00" level=info msg="ClientConn switching balancer to \"pick_first\"" module=grpc oct 31 14:44:12 dappnode kernel: overlayfs: upper fs needs to support d_type. oct 31 14:44:12 dappnode kernel: overlayfs: upper fs does not support tmpfile. oct 31 14:44:12 dappnode kernel: overlayfs: upper fs does not support RENAME_WHITEOUT. oct 31 14:44:12 dappnode kernel: overlayfs: upper fs does not support xattr, falling back to index=off and metacopy=off. oct 31 14:44:12 dappnode systemd[4402]: var-lib-unraidDocker-overlay2-check\x2doverlayfs\x2dsupport666682451-merged.mount: Succeeded. ░░ Subject: Unit succeeded ░░ Defined-By: systemd ░░ Support: https://www.debian.org/support ░░ ░░ The unit UNIT has successfully entered the 'dead' state. oct 31 14:44:12 dappnode systemd[1]: var-lib-unraidDocker-overlay2-check\x2doverlayfs\x2dsupport666682451-merged.mount: Succeeded. ░░ Subject: Unit succeeded ░░ Defined-By: systemd ░░ Support: https://www.debian.org/support ░░ ░░ The unit var-lib-unraidDocker-overlay2-check\x2doverlayfs\x2dsupport666682451-merged.mount has successfully entered the 'dead' state. oct 31 14:44:12 dappnode dockerd[8204]: time="2020-10-31T14:44:12.358626706+01:00" level=warning msg="overlay2: the backing <unknown> filesystem is formatted without d_type support, which leads to incorr> oct 31 14:44:12 dappnode dockerd[8204]: time="2020-10-31T14:44:12.359865909+01:00" level=info msg="[graphdriver] using prior storage driver: overlay2" oct 31 14:44:13 dappnode dockerd[8204]: failed to start daemon: error while opening volume store metadata database: invalid argument oct 31 14:44:13 dappnode systemd[1]: docker.service: Main process exited, code=exited, status=1/FAILURE ░░ Subject: Unit process exited ░░ Defined-By: systemd ░░ Support: https://www.debian.org/support ░░ ░░ An ExecStart= process belonging to unit docker.service has exited. ░░ ░░ The process' exit code is 'exited' and its exit status is 1. oct 31 14:44:13 dappnode systemd[1]: docker.service: Failed with result 'exit-code'. ░░ Subject: Unit failed ░░ Defined-By: systemd ░░ Support: https://www.debian.org/support ░░ ░░ The unit docker.service has entered the 'failed' state with result 'exit-code'. oct 31 14:44:13 dappnode systemd[1]: Failed to start Docker Application Container Engine. ░░ Subject: A start job for unit docker.service has failed ░░ Defined-By: systemd ░░ Support: https://www.debian.org/support ░░ ░░ A start job for unit docker.service has finished with a failure. ░░ ░░ The job identifier is 2219 and the job result is failed. lines 3066-3127/3127 (END)
October 31, 20205 yr Author A new try: 1. Added to /etc/initramfs -u 9p 9pnet 9pnet_virtio then: sudo update-initramfs -u A net error as a result: root@dappnode:~# systemctl daemon-reload root@dappnode:~# sudo systemctl start docker Job for docker.service failed because the control process exited with error code. See "systemctl status docker.service" and "journalctl -xe" for details. root@dappnode:~# journalctl -xe ░░ Support: https://www.debian.org/support ░░ ░░ A start job for unit docker.socket has finished successfully. ░░ ░░ The job identifier is 4040. oct 31 19:31:05 dappnode systemd[1]: Starting Docker Application Container Engine... ░░ Subject: A start job for unit docker.service has begun execution ░░ Defined-By: systemd ░░ Support: https://www.debian.org/support ░░ ░░ A start job for unit docker.service has begun execution. ░░ ░░ The job identifier is 3950. oct 31 19:31:05 dappnode dockerd[7597]: time="2020-10-31T19:31:05.192037421+01:00" level=info msg="Starting up" oct 31 19:31:05 dappnode dockerd[7597]: time="2020-10-31T19:31:05.209365291+01:00" level=info msg="parsed scheme: \"unix\"" module=grpc oct 31 19:31:05 dappnode dockerd[7597]: time="2020-10-31T19:31:05.209406349+01:00" level=info msg="scheme \"unix\" not registered, fallback to default scheme" module=grpc oct 31 19:31:05 dappnode dockerd[7597]: time="2020-10-31T19:31:05.209440999+01:00" level=info msg="ccResolverWrapper: sending update to cc: {[{unix:///run/containerd/containerd.sock 0 <nil>}] <nil>}" mo> oct 31 19:31:05 dappnode dockerd[7597]: time="2020-10-31T19:31:05.209461458+01:00" level=info msg="ClientConn switching balancer to \"pick_first\"" module=grpc oct 31 19:31:05 dappnode dockerd[7597]: time="2020-10-31T19:31:05.213446336+01:00" level=info msg="parsed scheme: \"unix\"" module=grpc oct 31 19:31:05 dappnode dockerd[7597]: time="2020-10-31T19:31:05.213472759+01:00" level=info msg="scheme \"unix\" not registered, fallback to default scheme" module=grpc oct 31 19:31:05 dappnode dockerd[7597]: time="2020-10-31T19:31:05.213486883+01:00" level=info msg="ccResolverWrapper: sending update to cc: {[{unix:///run/containerd/containerd.sock 0 <nil>}] <nil>}" mo> oct 31 19:31:05 dappnode dockerd[7597]: time="2020-10-31T19:31:05.213495262+01:00" level=info msg="ClientConn switching balancer to \"pick_first\"" module=grpc oct 31 19:31:05 dappnode kernel: overlayfs: upper fs needs to support d_type. oct 31 19:31:05 dappnode kernel: overlayfs: upper fs does not support tmpfile. oct 31 19:31:05 dappnode kernel: overlayfs: upper fs does not support RENAME_WHITEOUT. oct 31 19:31:05 dappnode kernel: overlayfs: upper fs does not support xattr, falling back to index=off and metacopy=off. oct 31 19:31:05 dappnode systemd[2107]: var-lib-mountedDocker-overlay2-check\x2doverlayfs\x2dsupport363317754-merged.mount: Succeeded. ░░ Subject: Unit succeeded ░░ Defined-By: systemd ░░ Support: https://www.debian.org/support ░░ ░░ The unit UNIT has successfully entered the 'dead' state. oct 31 19:31:05 dappnode systemd[1]: var-lib-mountedDocker-overlay2-check\x2doverlayfs\x2dsupport363317754-merged.mount: Succeeded. ░░ Subject: Unit succeeded ░░ Defined-By: systemd ░░ Support: https://www.debian.org/support ░░ ░░ The unit var-lib-mountedDocker-overlay2-check\x2doverlayfs\x2dsupport363317754-merged.mount has successfully entered the 'dead' state. oct 31 19:31:05 dappnode dockerd[7597]: time="2020-10-31T19:31:05.331722926+01:00" level=warning msg="overlay2: the backing <unknown> filesystem is formatted without d_type support, which leads to incorr> oct 31 19:31:06 dappnode dockerd[7597]: failed to start daemon: error while opening volume store metadata database: invalid argument oct 31 19:31:06 dappnode systemd[1]: docker.service: Main process exited, code=exited, status=1/FAILURE ░░ Subject: Unit process exited ░░ Defined-By: systemd ░░ Support: https://www.debian.org/support ░░ ░░ An ExecStart= process belonging to unit docker.service has exited. ░░ ░░ The process' exit code is 'exited' and its exit status is 1. oct 31 19:31:06 dappnode systemd[1]: docker.service: Failed with result 'exit-code'. ░░ Subject: Unit failed ░░ Defined-By: systemd ░░ Support: https://www.debian.org/support ░░ ░░ The unit docker.service has entered the 'failed' state with result 'exit-code'. oct 31 19:31:06 dappnode systemd[1]: Failed to start Docker Application Container Engine. ░░ Subject: A start job for unit docker.service has failed ░░ Defined-By: systemd ░░ Support: https://www.debian.org/support ░░ ░░ A start job for unit docker.service has finished with a failure. ░░ ░░ The job identifier is 3950 and the job result is failed.
January 16, 20242 yr If anybody else has this problem, just use virtiofs instead of 9p as the Unraid Share Mode for the share and it should work fine. At least it did for me
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.