SVI/ProxmoxVE
1
0
Fork 0
mirror of https://github.com/community-scripts/ProxmoxVE.git synced 2026-07-02 20:21:55 -04:00
Code Issues 2.6k Packages Projects Releases 10 Wiki Activity

Vikunja install error #53

New Issue
Closed
opened 2025-11-20 04:43:02 -05:00 by saavagebueno · 4 comments
saavagebueno commented 2025-11-20 04:43:02 -05:00
Owner
Copy Link

Originally created by @ranebrown on GitHub (Nov 14, 2024).

Please verify that you have read and understood the guidelines.

yes

A clear and concise description of the issue.

Vikunja install fails with below error. No additional information if running advanced mode with verbose logging.

What settings are you currently utilizing?

Default Settings

Which Linux distribution are you employing?

Debian 12

If relevant, including screenshots or a code block can be helpful in clarifying the issue.

Creating a Vikunja LXC using the above default settings
 ✓ Using local for Template Storage.
 ✓ Using local-lvm for Container Storage.
 ✓ Updated LXC Template List
 \unable to create CT 109 - command 'lxc-usernsexec -m u:0:100000:65536 -m g:0:100000:65536 -- tar xpf - --zstd --totals --one-file-system -p --sparse --numeric-owner --acls --xattrs '--xattrs-include=user.*' '--xattrs-include=security.capability' '--warning=no-file-ignored' '--warning=no-xattr-write' -C /var/lib/lxc/109/rootfs --skip-old-files --anchored --exclude './dev/*'' failed: exit code 2
 |bash: line 182: exit: A problem occured while trying to create container.: numeric argument required

Please provide detailed steps to reproduce the issue.

Attempt default install by pasting bash -c "$(wget -qLO - https://github.com/community-scripts/ProxmoxVE/raw/main/ct/vikunja.sh)" into shell.

Originally created by @ranebrown on GitHub (Nov 14, 2024). ### Please verify that you have read and understood the guidelines. yes ### A clear and concise description of the issue. Vikunja install fails with below error. No additional information if running advanced mode with verbose logging. ### What settings are you currently utilizing? Default Settings ### Which Linux distribution are you employing? Debian 12 ### If relevant, including screenshots or a code block can be helpful in clarifying the issue. ``` Creating a Vikunja LXC using the above default settings ✓ Using local for Template Storage. ✓ Using local-lvm for Container Storage. ✓ Updated LXC Template List \unable to create CT 109 - command 'lxc-usernsexec -m u:0:100000:65536 -m g:0:100000:65536 -- tar xpf - --zstd --totals --one-file-system -p --sparse --numeric-owner --acls --xattrs '--xattrs-include=user.*' '--xattrs-include=security.capability' '--warning=no-file-ignored' '--warning=no-xattr-write' -C /var/lib/lxc/109/rootfs --skip-old-files --anchored --exclude './dev/*'' failed: exit code 2 |bash: line 182: exit: A problem occured while trying to create container.: numeric argument required ``` ### Please provide detailed steps to reproduce the issue. Attempt default install by pasting `bash -c "$(wget -qLO - https://github.com/community-scripts/ProxmoxVE/raw/main/ct/vikunja.sh)"` into shell.
saavagebueno added the not a script issue label 2025-11-20 04:43:02 -05:00
saavagebueno commented 2025-11-20 04:43:03 -05:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Nov 14, 2024):

Thats not an vikunja issue, the script failed, because there are some problems on your proxmox node with the container id or something else.

Reboot your Proxmox and test again

@MickLesk commented on GitHub (Nov 14, 2024): Thats not an vikunja issue, the script failed, because there are some problems on your proxmox node with the container id or something else. Reboot your Proxmox and test again
saavagebueno commented 2025-11-20 04:43:03 -05:00
Author
Owner
Copy Link

@ranebrown commented on GitHub (Nov 14, 2024):

Rebooting didn't help but I am seeing the same error trying a different script. Any advice on how to debug this?

@ranebrown commented on GitHub (Nov 14, 2024): Rebooting didn't help but I am seeing the same error trying a different script. Any advice on how to debug this?
saavagebueno commented 2025-11-20 04:43:03 -05:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Nov 14, 2024):

Which version of Proxmox VE? With which user do you run the script? Do you run the script in Main-Node?

nano /etc/subuid
nano /etc/subgid

Whats the output?

@MickLesk commented on GitHub (Nov 14, 2024): Which version of Proxmox VE? With which user do you run the script? Do you run the script in Main-Node? nano /etc/subuid nano /etc/subgid Whats the output?
saavagebueno commented 2025-11-20 04:43:03 -05:00
Author
Owner
Copy Link

@ranebrown commented on GitHub (Nov 14, 2024):

Got it fixed. There was a leftover folder in /var/lib/lxc with incorrect permissions that matched the new id I was trying to use. Deleting that folder and allowing it to be recreated worked. Thanks for the help.

@ranebrown commented on GitHub (Nov 14, 2024): Got it fixed. There was a leftover folder in `/var/lib/lxc` with incorrect permissions that matched the new id I was trying to use. Deleting that folder and allowing it to be recreated worked. Thanks for the help.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
🛑 Failure to comply with the guidelines
breaking change
bug
bug
bugfix
deferred
delete script
dependencies
enhancement
external
feature
github
help wanted
Implemented in VED waiting push to Main
in project pipeline
invalid
investigation
json
maintenance
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
No Label not a script issue
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
saavagebueno
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: SVI/ProxmoxVE#53
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?