Wrong uid and gid on consume and export folder?

[JMarschner]

I run in some problems with privileges at new installation.
To install paperless-ngx i use the easy install docker script. (https://docs.paperless-ngx.com/setup/#docker_script)
Because my user has the uid 1000 and gid 1000 I left this blank. But the consum and export folder will be created with an owner 100999:100999.

After figuring this out, I added the following to docker-compose.env:
USERMAP_UID=1000
USERMAP_GID=1000

I also change the web server user at docker-compose.yml:
webserver:
image: ghcr.io/paperless-ngx/paperless-ngx:latest
user: "1000:1000"

But the issue is still there. The privileges on consume and export folder will not map correct.
Does anyone know this problem? Is there a solution for this?

Thanks in advance for your help!

[stumpylog]

Unless you have a very particular situation, you should only set one of the USERMAP_ or user:. One is used by paperless, the other you should read the Docker documentation for.

[JMarschner]

Yes I know.

Actually, I shouldn't have to set either option. But without or only with USERMAP_ always means that the rights of the folder are set to user 100999:100999. (No actual user)

If I set USERMAP_ to 100:100 the owning user changes to 100099:100099.
With USERMAP_ 2000:2000 the owning user is set to 101999.

I think it's really strange.

[stumpylog]

You can easily check the UID/GID of the paperless user. From inside the container: id -u paperless and id -g paperless. If they're set as per the USERMAP_ variables, you must be running into something Docker related.

[JMarschner]

Thank you for your quick response!
The command docker exec paperless-webserver-1 id paperless returns
uid=1000(paperless) gid=1000(paperless) groups=1000(paperless)
It actually looks good in the container.
Probably a docker thing after all?

[stumpylog]

It seems likely in this case. Docker can do some odd things with users and mappings back to the host

[github-actions[bot]]

This discussion has been automatically closed due to inactivity.

[github-actions[bot]]

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.