Trying to move /var/lib/docker to another drive

dmryce · 26. Januar 2020

I have am running OMV 4.1.32-1 on a Raspberry Pi 3B+. I have been trying to move the /var/lib/docker to a data drive and keep getting an error. I made the following changes:

1) Edited /etc/openmediavault/config.xml to replace noexec with exec in
the <fstab> <mntent> sections. and ran omv-mkconf
fstab

2) Edited /etc/default/openmediavault and added
OMV_FSTAB_MNTOPS_EXT4="defaults,nofail,user_xattr,exec,usrjquota=aquota.user,grpjquota=aquota.group,jqfmt=vfsv0"

Then:

Code

service docker stop

Created daemon.json under the directory /etc/docker

Code

{  
 "graph": "/srv/dev-disk-by-id-ata-ST4000LM016-1N2170_W801F924-part2/docker"
}

Code

rsync -aP /var/lib/docker/ /srv/dev-disk-by-id-ata-ST4000LM016-1N2170_W801F924-part2/docker

The files copy successfully to their new location.

Code

mv /var/lib/docker /var/lib/docker.old

Code

service docker start

The service starts correctly, but the container will not start. Instead I receive the following error:

Code

Failed to execute command 'export PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin; export LANG=C.UTF-8; docker start 40870bc8d8ad 2>&1' with exit code '1': Error response from daemon: error creating overlay mount to /srv/dev-disk-by-id-ata-ST4000LM016-1N2170_W801F924-part2/docker/overlay2/7e988acd17fcafdbaeda53bb9d7a7212f8149ca7d74a959fa715f05ee3a25f7f/merged: invalid argument Error: failed to start containers: 40870bc8d8ad
OMV\ExecException: Failed to execute command 'export PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin; export LANG=C.UTF-8; docker start 40870bc8d8ad 2>&1' with exit code '1': Error response from daemon: error creating overlay mount to /srv/dev-disk-by-id-ata-ST4000LM016-1N2170_W801F924-part2/docker/overlay2/7e988acd17fcafdbaeda53bb9d7a7212f8149ca7d74a959fa715f05ee3a25f7f/merged: invalid argument
Error: failed to start containers: 40870bc8d8ad in /usr/share/php/openmediavault/system/process.inc:182


Stack trace:
#0 /usr/share/openmediavault/engined/rpc/docker.inc(728): OMV\System\Process->execute()
#1 [internal function]: OMVRpcServiceDocker->startContainer(Array, Array)
#2 /usr/share/php/openmediavault/rpc/serviceabstract.inc(123): call_user_func_array(Array, Array)
#3 /usr/share/php/openmediavault/rpc/rpc.inc(86): OMV\Rpc\ServiceAbstract->callMethod('startContainer', Array, Array)
#4 /usr/sbin/omv-engined(537): OMV\Rpc\Rpc::call('Docker', 'startContainer', Array, Array, 1)
#5 {main}

Alles anzeigen

When I change the path back to /var/lib/docker everything works as expected, so I know I'm missing a step somewhere. I have searched the forum, but I just can't seem to figure out. Thanks so much for any guidance you all can provide.

gderf · 26. Januar 2020

Did you verify that the drive you want to be mounted exec is actually mounted exec? Look in /etc/fstab.

Did you remount all drives or reboot?

dmryce · 27. Januar 2020

Zitat von gderf

Did you verify that the drive you want to be mounted exec is actually mounted exec? Look in /etc/fstab.

Did you remount all drives or reboot?

Thank you so much! I forgot that the drive I was trying to use is formatted ntfs, so it was not mounting exec using my existing parameters for that drive. Once I switched to the ext4 volume that was setup to mount exec in fstab the container started working properly. I really appreciate all of your help. Have a great night!

bbouton · 27. Januar 2020

I also think that 'graph' in the /etc/docker/daemon.json is no longer the key depending on your version of docker. I think it is now 'docker_root'. I would have to look at mine later. No matter as from what I remember it was the only thing in the file for me anyway.

Jetzt mitmachen!