After fixing my initial issue, I'm confused as to how to best setup the permissions on the host for the volumes.
Unless I set all the folders on the host to nobody:root the services in the containers don't work properly. However, setting them to nobody:root makes accessing the data inconvenient for other users on the system.
There's probably a better way of doing it and I presume you have set up something for this on your own system.
Googling the issue gave me that I should run data only containers and then link them. Which is fine until the fact that the data only container still needs access to the host.
The reason I want to keep the files on the host, is so that I can house them on my ZFS pool - instead of keeping the data in the containers - /var/lib/docker or somewhere.
After fixing my initial issue, I'm confused as to how to best setup the permissions on the host for the volumes.
Unless I set all the folders on the host to nobody:root the services in the containers don't work properly. However, setting them to nobody:root makes accessing the data inconvenient for other users on the system.
There's probably a better way of doing it and I presume you have set up something for this on your own system.
Googling the issue gave me that I should run data only containers and then link them. Which is fine until the fact that the data only container still needs access to the host.
The reason I want to keep the files on the host, is so that I can house them on my ZFS pool - instead of keeping the data in the containers - /var/lib/docker or somewhere.