starred/ProxmoxVE
1
0
Fork 0
mirror of https://github.com/community-scripts/ProxmoxVE.git synced 2026-02-05 00:29:55 +03:00
Code Issues 11 Packages Projects Releases 10 Wiki Activity

paperless-ngx uv migration failed #1535

New Issue
Closed
opened 2026-02-05 01:29:32 +03:00 by OVERLORD · 7 comments
OVERLORD commented 2026-02-05 01:29:32 +03:00
Owner
Copy Link

Originally created by @Koersten on GitHub (Aug 26, 2025).

✅ Have you read and understood the above guidelines?

yes

📜 What is the name of the script you are using?

paperless-ngx

📂 What was the exact command used to execute the script?

bash -c "$(wget -qLO - https://github.com/community-scripts/ProxmoxVE/raw/main/ct/paperless-ngx.sh)"

⚙️ What settings are you using?

  • Default Settings
  • Advanced Settings

🖥️ Which Linux distribution are you using?

Debian 12

📝 Provide a clear and concise description of the issue.

I tried to update my paperless-ngx LXC and the uv migration failed due to an ownership issue that I do not understand.

🔄 Steps to reproduce the issue.

Run the script and try to update paperless-ngx from V2.18.1 to V2.18.2.

❌ Paste the full error output (if available).

____                        __

/ __ ____ _____ ___ / / __________ ____ ____ __ __
/ // / __ / __ \/ _ \/ ___/ / _ \/ ___/ ___/_____/ __ \/ __ / |//
/ __/ // / // / / / / / ( | )/ / / / // /> <
// _,/ ./_// //__/// // //_, //||
// /____/

✔️ Stopped all Paperless-ngx Services
✔️ Backup completed
⏳ Setup uv 0.8.13tar: uv-x86_64-unknown-linux-gnu/uv: Cannot change ownership to uid 1001, gid 117: Invalid argument
tar: uv-x86_64-unknown-linux-gnu/uvx: Cannot change ownership to uid 1001, gid 117: Invalid argument
tar: uv-x86_64-unknown-linux-gnu: Cannot change ownership to uid 1001, gid 117: Invalid argument
tar: Exiting with failure status due to previous errors
✖️ Failed to extract uv archive

[ERROR] in line 48: exit code 0: while executing command return 1

🖼️ Additional context (optional).

No response

Originally created by @Koersten on GitHub (Aug 26, 2025). ### ✅ Have you read and understood the above guidelines? yes ### 📜 What is the name of the script you are using? paperless-ngx ### 📂 What was the exact command used to execute the script? bash -c "$(wget -qLO - https://github.com/community-scripts/ProxmoxVE/raw/main/ct/paperless-ngx.sh)" ### ⚙️ What settings are you using? - [x] Default Settings - [ ] Advanced Settings ### 🖥️ Which Linux distribution are you using? Debian 12 ### 📝 Provide a clear and concise description of the issue. I tried to update my paperless-ngx LXC and the uv migration failed due to an ownership issue that I do not understand. ### 🔄 Steps to reproduce the issue. Run the script and try to update paperless-ngx from V2.18.1 to V2.18.2. ### ❌ Paste the full error output (if available). ____ __ / __ \____ _____ ___ _____/ /__ __________ ____ ____ __ __ / /_/ / __ `/ __ \/ _ \/ ___/ / _ \/ ___/ ___/_____/ __ \/ __ `/ |/_/ / ____/ /_/ / /_/ / __/ / / / __(__ |__ )_____/ / / / /_/ /> < /_/ \__,_/ .___/\___/_/ /_/\___/____/____/ /_/ /_/\__, /_/|_| /_/ /____/ ✔️ Stopped all Paperless-ngx Services ✔️ Backup completed ⏳ Setup uv 0.8.13tar: uv-x86_64-unknown-linux-gnu/uv: Cannot change ownership to uid 1001, gid 117: Invalid argument tar: uv-x86_64-unknown-linux-gnu/uvx: Cannot change ownership to uid 1001, gid 117: Invalid argument tar: uv-x86_64-unknown-linux-gnu: Cannot change ownership to uid 1001, gid 117: Invalid argument tar: Exiting with failure status due to previous errors ✖️ Failed to extract uv archive [ERROR] in line 48: exit code 0: while executing command return 1 ### 🖼️ Additional context (optional). _No response_
OVERLORD added the bug label 2026-02-05 01:29:32 +03:00
OVERLORD commented 2026-02-05 01:29:38 +03:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Aug 26, 2025):

curl -LsSf https://astral.sh/uv/install.sh | sh

Whats the Output

@MickLesk commented on GitHub (Aug 26, 2025): curl -LsSf https://astral.sh/uv/install.sh | sh Whats the Output
OVERLORD commented 2026-02-05 01:29:45 +03:00
Author
Owner
Copy Link

@Koersten commented on GitHub (Aug 26, 2025):

curl -LsSf https://astral.sh/uv/install.sh | sh

Whats the Output

curl -LsSf https://astral.sh/uv/install.sh | sh

downloading uv 0.8.13 x86_64-unknown-linux-gnu
no checksums to verify
tar: uv: Cannot change ownership to uid 1001, gid 117: Invalid argument
tar: uvx: Cannot change ownership to uid 1001, gid 117: Invalid argument
tar: Exiting with failure status due to previous errors
ERROR: command failed: tar xf /tmp/tmp.nOszbrJw79/input.tar.gz --strip-components 1 -C /tmp/tmp.nOszbrJw79

@Koersten commented on GitHub (Aug 26, 2025): > curl -LsSf https://astral.sh/uv/install.sh | sh > > Whats the Output curl -LsSf https://astral.sh/uv/install.sh | sh downloading uv 0.8.13 x86_64-unknown-linux-gnu no checksums to verify tar: uv: Cannot change ownership to uid 1001, gid 117: Invalid argument tar: uvx: Cannot change ownership to uid 1001, gid 117: Invalid argument tar: Exiting with failure status due to previous errors ERROR: command failed: tar xf /tmp/tmp.nOszbrJw79/input.tar.gz --strip-components 1 -C /tmp/tmp.nOszbrJw79
OVERLORD commented 2026-02-05 01:29:47 +03:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Aug 26, 2025):

Your whole LXC is broken with uid rights, try this (its not an Script issue):

curl -LO https://github.com/astral-sh/uv/releases/download/0.8.13/uv-x86_64-unknown-linux-gnu.tar.gz
tar --no-same-owner -xzf uv-x86_64-unknown-linux-gnu.tar.gz
mv uv /usr/local/bin/
mv uvx /usr/local/bin/

@MickLesk commented on GitHub (Aug 26, 2025): Your whole LXC is broken with uid rights, try this (its not an Script issue): curl -LO https://github.com/astral-sh/uv/releases/download/0.8.13/uv-x86_64-unknown-linux-gnu.tar.gz tar --no-same-owner -xzf uv-x86_64-unknown-linux-gnu.tar.gz mv uv /usr/local/bin/ mv uvx /usr/local/bin/
OVERLORD commented 2026-02-05 01:29:50 +03:00
Author
Owner
Copy Link

@Koersten commented on GitHub (Aug 26, 2025):

Thank you sir! You have saved my evening and helping me out. After doing that I could update my container as usual.
Sorry for creating an issue if it is not related to the work here.

The uid trouble may come from me mounting external directories into the container although I have to admit I do not fully understand why this leads to this problem.

@Koersten commented on GitHub (Aug 26, 2025): Thank you sir! You have saved my evening and helping me out. After doing that I could update my container as usual. Sorry for creating an issue if it is not related to the work here. The uid trouble may come from me mounting external directories into the container although I have to admit I do not fully understand why this leads to this problem.
OVERLORD commented 2026-02-05 01:29:53 +03:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Aug 26, 2025):

The issue happens because the uv tarball contains files owned by fixed UIDs/GIDs (1001:117)

In a normal unprivileged LXC, extracting works as long as it stays inside the container’s rootfs.

But when you mount external host directories into the container, tar tries to chown 1001:117 on those host paths.

Since that UID/GID isn’t mapped in the container’s user namespace, the kernel rejects it with Invalid argument output

Using tar --no-same-owner fixes it, because tar then ignores the archive’s UID/GID and just assigns ownership to the extracting user (root in the container).

In short; the error comes from UID/GID mismatch when extracting into a mounted host directory inside an unprivileged LXC

@MickLesk commented on GitHub (Aug 26, 2025): The issue happens because the uv tarball contains files owned by fixed UIDs/GIDs (1001:117) In a normal unprivileged LXC, extracting works as long as it stays inside the container’s rootfs. But when you mount external host directories into the container, tar tries to chown 1001:117 on those host paths. Since that UID/GID isn’t mapped in the container’s user namespace, the kernel rejects it with Invalid argument output Using tar --no-same-owner fixes it, because tar then ignores the archive’s UID/GID and just assigns ownership to the extracting user (root in the container). In short; the error comes from UID/GID mismatch when extracting into a mounted host directory inside an unprivileged LXC
OVERLORD commented 2026-02-05 01:29:58 +03:00
Author
Owner
Copy Link

@Koersten commented on GitHub (Aug 26, 2025):

Thank you for the explanation! Learned something today.
This may be why I should stay the hardware engineer I am...

@Koersten commented on GitHub (Aug 26, 2025): Thank you for the explanation! Learned something today. This may be why I should stay the hardware engineer I am...
OVERLORD commented 2026-02-05 01:30:04 +03:00
Author
Owner
Copy Link

@thomaskoopmans commented on GitHub (Aug 31, 2025):

Thanks for the fix, I have the same issue with an Immich lxc which I created a few days ago with the install script (all standard settings).
The update script fails on the uv chown thing. Any suggestions on how to use the update script?

@thomaskoopmans commented on GitHub (Aug 31, 2025): Thanks for the fix, I have the same issue with an Immich lxc which I created a few days ago with the install script (all standard settings). The update script fails on the uv chown thing. Any suggestions on how to use the update script?
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Implemented in VED waiting push to Main
breaking change
bug
bug
bugfix
deferred
delete script
dependencies
enhancement
external
feature
github
help wanted
in project pipeline
invalid
investigation
json
maintenance
needs triage
new script
new script
nice to have
not a script issue
not planned
organization
pull-request
Mirrored from GitHub Pull Request
 question
refactor
rename script
security
update script
website
wontdo
🛑 Failure to comply with the guidelines
No Label bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
OVERLORD
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/ProxmoxVE#1535
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?