Is this a new install with no container data or are you trying to move containers that are already configured and working
New install with no container data at all. I've not installed Docker at all yet.
I have a dedicated drive with a share created I'd like to have as a target for docker storage. The last time I tried this i think supplied the folder in the wrong format...I used something like 'DockerStuff/' and the install fouled up.
Before I installed docker I changed the docker storage path to a folder in one of my mounted drives.
The folder did not need to be a shared folder.
The docker install created the folder I specified in the location and the permissions were set.
I would say set your path first then save the setting then install docker.
And don't set it to a shared folder. Just set it to a folder in one of your mounted drives and the docker install should create it for you.
In my install:
/srv/dev-disk-by-label[disklabel]/nameOfDockerFolder
You would find this information in your disks section of the web gui.
The [disklabel] is what your disk is called and the nameofDockerFolder is whatever you want the folder to be called.
New install with no container data at all. I've not installed Docker at all yet.
I have a dedicated drive with a share created I'd like to have as a target for docker storage. The last time I tried this i think supplied the folder in the wrong format...I used something like 'DockerStuff/' and the install fouled up.
[attach='17134','none','false'][/attach
If there is no existing docker data, then just enter the absolute path to the existing directory you have set up for this in the Docker Storage box.
Alles anzeigenIn my install:
/srv/dev-disk-by-label[disklabel]/nameOfDockerFolder
You would find this information in your disks section of the web gui.
The [disklabel] is what your disk is called and the nameofDockerFolder is whatever you want the folder to be called.
so would my path then be:
/srv/dev-disk-by-label/LookingGlass/DockerStorage
/srv/dev/disk/by-label/LookingGlass/DockerStorage
?? sorry for the dumb questions.
Your paths look different from mine.
When I ssh into my omv and do ls / I see a directory labeled srv.
ls /srv then shows me the rest of my mounted drives.
Wherever your mounted drives show that's the path you would use. According to your webui that is /dev. I have most of my drives mounted the default way (/srv) so I can't assume how your devices are mounted.
/dev path is the device path. You don't want to use that. You want to use the /srv path. If you look in shared folders and add the absolute path column, you can see the full path of each shared folder.
/srv/dev-disk-by-label/LookingGlass/DockerStorage
should be
/srv/dev-disk-by-label-LookingGlass/DockerStorage
Hmh, interesting. Never thought about this. I'm running OMV from an NVMe SSD M.2 drive. I have sufficient space on there, but just started wondering about "wear and tear". Would you guys recommend moving the docker folder to the HDD Raid instead? And if so, how would you do that with containers being installed?
I have sufficient space on there, but just started wondering about "wear and tear". Would you guys recommend moving the docker folder to the HDD Raid instead? And if so, how would you do that with containers being installed?
Your nvme life should be plenty long to not worry about. Also, if your config and data volumes for docker are stored on the OS drive, that is a bit tougher to move. If they aren't, you can just move the docker directory and recreate your containers with the same volumes.
Yes, my config and data folders are on the raid already. But OK, I'll leave the docker directory itself on the OS NVME drive then. Thanks for your advice, ryecoaaron.
Yes, my config and data folders are on the raid already. But OK, I'll leave the docker directory itself on the OS NVME drive then. Thanks for your advice, ryecoaaron.
Installation and Setup Videos - Beginning, Intermediate and Advanced
scroll down a few fids
Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!
