I use namespace for isolate my containers but I can't start FoundryVTT if I use docker namespace. I have a error like ' chown "Operation not permitted" ' (on all the data repertory) on the startup when (I think) it try to bind my local data to the container.
$ docker-compose up
[...] Start [...]
foundry | chown: /data/[...]: Operation not permitted
Expected behavior
I don't want to use "userns_mode: host" in my docker-compose for bypass my configuration.
In this case the contenair is launch with privilege (it's a secrurity issue).
user: foundry:foundry (or root) in docker-compose dont solve the problem.
Bug description
I use namespace for isolate my containers but I can't start FoundryVTT if I use docker namespace. I have a error like ' chown "Operation not permitted" ' (on all the data repertory) on the startup when (I think) it try to bind my local data to the container.
Thanks for your help
Steps to reproduce
$ nano /etc/docker/daemon.json { "userns-remap": "default", }
$ systemctl daemon-reload $ systemctl restart docker
$ docker-compose up [...] Start [...] foundry | chown: /data/[...]: Operation not permitted
Expected behavior
I don't want to use "userns_mode: host" in my docker-compose for bypass my configuration. In this case the contenair is launch with privilege (it's a secrurity issue). user: foundry:foundry (or root) in docker-compose dont solve the problem.
Container metadata
Relevant log output
Code of Conduct