Unarchive task fails if paperless_ngx_conf_usermap_uid != 1000

[borismw]

Steps to reproduce:

• run this paperless-ngx role with paperless_ngx_conf_usermap_uid != 1000

What happens?

• On the following tasks the program doing the actual unpacking fails with bad address
  • tasks/base_dependencies/python.yml -> Download and extract python sources
  • tasks/paperless_ngx/release_files.yml -> Download and extract paperless-ngx

---

Hi 👋🏾
thanks a lot for this ansible role, it is great work and I really appreciate it. I noticed that when I choose a uid other than 1000 for the paperlessngx system user, the ansible.builtin.unarchive step fails. Since the files in the archives are owned by a user with the uid 1000 the untar process refuses to change its ownership. This happens even though the tasks are have the become field set to true. I hope this is reproducible. I will come up with a PR #240 with a proposal on how to fix this issue.

[stevenengland]

Hi @borismw thanks for reporting and providing a PR. I'll have a look into the whole topic soon. For a holistic approach, I need to see what solution fits best here (as you mention in your PR as well).

[borismw]

Thank you for taking the time to consider this. To add some context: I am currently using this role for setting up paperless-ngx in an LXD container on a QNAP TS451+. But I was also able to reproduce this issue in a Ubuntu 24.04 VM on my PC. Maybe important to note: In both cases I am using ansible-pull, so the extraction process takes place on the same host paperless-ngx is being deployed to. If I understood correctly this makes a difference to the "regular" way where the extraction process might run on a different host that the one the files are deployed to. In the "regular" case, maybe changing the uid of the paperless_system_user does not fix the problem at all. 🤔