I’ve been using Docker on Unraid and love it! I’m branching out and starting to run containers on Debian 12 VMs, but I’m running into issues with bind mounts.
This happens with all containers I try to run, so I’m sure I’m doing something wrong.
When I start a new container, should it automatically create the folders it needs when it starts up?
When you bind a host path, the owner and permissions on the host filesystem path must match the process of the container, unless the image takes care of fixing ownership and/or permission. A container based on this image doesn’t fix it.
Either one of these approaches work:
use a named volume instead a host path
create the folder and chmod 777 it: mkdir -p rundeck && chmod 777 rundeck
create the folder and chown 1000:0 it: mkdir -p rundeck && chown 1000:0 rundeck
I looked the uid and gid up from inside the container, as I couldn’t find it mentioned in the docs.