My data path within my containers resets every time I reboot my system. I've set the path to a directory in a Union filesystem, although every time I reboot my device the data path is set to my boot drive. The boot drive is standalone from the Union drives, it holds no data other than the OS. Any idea why this might be happening ?
Docker Data path resets upon reboot
-
- OMV 4.x
- gelöst
- Jacobo1223
-
-
your unionFS is mounted after docker, so please use a path that point directly to one of your disk.
-
your unionFS is mounted after docker, so please use a path that point directly to one of your disk.
I've Had no issues with my config files which are bound to a directory on my unionFS ? Surely it would affect both systems not just the data. Also my UnionFS is set to Most free space, so when the files are transferred from the /data directory into my organised file directories surely the data wouldn't move between the disks because it's already in the UnionFS so one drive would hold all the data and the others would be empty ?
-
-
I've Had no issues with my config files which are bound to a directory on my unionFS ? Surely it would affect both systems not just the data. Also my UnionFS is set to Most free space, so when the files are transferred from the /data directory into my organised file directories surely the data wouldn't move between the disks because it's already in the UnionFS so one drive would hold all the data and the others would be empty ?
Alright I've done some experimenting with my drives and found that it's quite annoying that unionFS mounts after docker. How could i change this, while still having my containers start upon boot ?
-
This may or may not help also their is a lot of information on github one of the default options is direct_io if you read through github that option is now deprecated.
Personally I don't have any problems but that is because anything Docker related is on a standalone drive, but there should be a logical solution.
-
For Anyone in the future with a similar issue, I've resolved it by using ZFS instead of UnionFS. Just get the Proxmox kernel and install through plugins.
-
Jetzt mitmachen!
Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!