mirror of
https://github.com/community-scripts/ProxmoxVE-Local.git
synced 2026-03-31 06:23:54 -04:00
Install script failed - Argument list too long #99
Reference in New Issue
Block a user
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?
Originally created by @Destiny971 on GitHub (Nov 9, 2025).
✅ Have you read and understood the above guidelines?
yes
📝 Provide a clear and concise description of the issue.
When I try to install a script via the web interface, I get the following error:
ct/../core/build.func: line 1147: /usr/bin/bash: Argument list too longAll scripts that I have tested are affected.
🔄 Steps to reproduce the issue.
For example, Docmost
Setp 1: load script
Step 2: Click install
Step 3: select server
Step 4: run on server
Step 5: select default settings
❌ Paste the full error output (if available).
⚙️ Using Default Settings on node pve-03
🆔 Container ID: 123
🖥️ Operating System: debian (13)
📦 Container Type: Unprivileged
💾 Disk Size: 8 GB
🧠 CPU Cores: 3
🛠️ RAM Size: 4096 MiB
🚀 Creating a Docmost LXC using the above default settings
ct/../core/build.func: line 1147: /usr/bin/bash: Argument list too long
[ERROR] in line 1147: exit code 0: while executing command bash "
CORE_DIR/create_lxc.sh"?[11:19:33] ✅ SSH script execution finished with code: 126
🖼️ Additional context (optional).
Issue on PVE 8.4.14 and 9.0.11
Using ProxmoxVE-Local v0.4.10
@wisehalvdan commented on GitHub (Nov 9, 2025):
I'm experiencing the same after updated to latest. Just using the shell command from hosted version runs fine on same hosts.
@michelroegl-brunner commented on GitHub (Nov 10, 2025):
The latest build.func did for some reason dont make it to the release, i added it. Please update to 0.4.10.2 when it is released.
@michelroegl-brunner commented on GitHub (Nov 10, 2025):
Also there is sadly a bug in the update script. After the Update please log into your LXC, edit the VERSION file and change the number to something else the 04.10.2 (0.4.10.1) for example and run the Update again.
@Destiny971 commented on GitHub (Nov 10, 2025):
Now it works. Thanks 👍