Replies: 6 comments 15 replies
|
That was adding #1212, perhaps @theEndBeta could explain more |
|
I am currently having the same problem. From what I can see, running rootless as described in the documentation fails if
because then we cannot run as user "paperless" as suggested by the documentation or by the discussion in #1212 . |
|
I had the same issue, after experimenting with the options, here's how it works for me (deployed in k8s, directory mounted over nfs): everything works as it should for me (I am ok with the uid 1000, it doesn't matter how it's called on the host, it's called "paperless" within the container": Note: don't forget to set PAPERLESS_CONSUMER_POLLING if you want to use consume directory mounted over nfs. |
|
I'm confused as to why |
|
This discussion has been automatically closed due to inactivity. Please see our contributing guidelines for more details. |
|
This discussion has been automatically locked since there has not been any recent activity after it was closed. Please open a new discussion for related concerns. See our contributing guidelines for more details. |
Uh oh!
There was an error while loading. Please reload this page.
Description
I can't setup the container as rootless. Following the docs instructions to set up the user inside the containr provokes a permissions error that dissapears when I uncomment the
userkey so the problem is in the key. Am I misunderstanding the usage of the keyuser? I have to admit that the docs could benefit of having the rootless section explained a little betterSteps to reproduce
I'm using docker compose and my
docker-compose.ymlfile looks like thisMy
docker-compose.envfile looks like thisand uid/gid information:
I want to run the container in rootless mode so I added
user: 1000:100underwebserver, which is the uid/gid of the user running the container, as per the docs:Webserver logs
that loops indefinitely
All reactions