Docmost LXC fails to install on Proxmox 8.3.1

[flinthamm]

✅ Have you read and understood the above guidelines?

yes

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

Docmost LXC

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

bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/docmost.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.

In trying to install this LXC script with the default settings in the Proxmox 6.8.12-5-pve shell, it just finishes installed dependencies when errors start and shortly afterwards the script is exited and the install fails.

🔄 Steps to reproduce the issue.

Run the install script in Proxmox shell and it fails to complete. Having checked previous issues DNS has been checked and no AD blocking or similar has been enabled.

❌ Paste the full error output (if available).

    ____                                  __ 
   / __ \____  _________ ___  ____  _____/ /_
  / / / / __ \/ ___/ __ `__ \/ __ \/ ___/ __/
 / /_/ / /_/ / /__/ / / / / / /_/ (__  ) /_  
/_____/\____/\___/_/ /_/ /_/\____/____/\__/  
                                             
  ⚙️  Using Default Settings on node proxmox
  🖥️  Operating System: debian
  🌟  Version: 12
  📦  Container Type: Unprivileged
  💾  Disk Size: 7 GB
  🧠  CPU Cores: 3
  🛠️  RAM Size: 3072 MiB
  🆔  Container ID: 1xx
  🚀  Creating a Docmost LXC using the above default settings
  
  ✔️  Using local for Template Storage.
  ✔️  Using local-lvm for Container Storage.
  ✔️  Updated LXC Template List
  ✔️  LXC Template is ready to use.
  ✔️  LXC Container 129 was successfully created.
  ✔️   Started LXC Container
  ✔️  Set up Container OS
  ✔️  Network Connected: 192.168.x.x 
  ✔️  IPv4 Internet Connected
  ✖️  IPv6 Internet Not Connected
  ✔️  DNS Resolved github.com to 20.26.156.215
  ✔️  Updated Container OS
  ✔️  Core dependencies installed
  ✔️  Installed Dependencies
0: line 22: jq: command not found
curl: (22) The requested URL returned error: 400
  ✔️  Installed Node.js 22
  ✖️  Failed to install pnpm@
/dev/fd/63: line 74: SPINNER_PID: unbound variable

🖼️ Additional context (optional).

No response

[dannyellis]

Looks like the refactor done in #4744 probably caused this

[MickLesk]

No, Run in verbose, it failed by source install of pnpm, i think Network or something

[dannyellis]

Doesn't appear jq was installed as part of the apt install. Here is your output in verbose. Might just need jq in the apt install

✔️ Installed Dependencies
0: line 22: jq: command not found
curl: (22) The requested URL returned error: 400
Reading package lists... Doneing version 22 Installing jq...
Building dependency tree... Done
Reading state information... Done
Package 'nodejs' is not installed, so not removed
⠏0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
✔️ Installed Node.js 22
⠴npm error code EINVALIDTAGNAME
npm error Invalid tag name "^[[?25h" of package "pnpm@^[[?25h": Tags may not have any characters that encodeURIComponent encodes.
npm error A complete log of this run can be found in: /root/.npm/_logs/2025-05-29T15_54_35_517Z-debug-0.log
✖️ Failed to install pnpm@
/dev/fd/63: line 74: SPINNER_PID: unbound variable
root@elitedesk-g6-2:~#

[tremor021]

if ! command -v jq &>/dev/null; then
    $STD msg_info "Installing jq..."
    $STD apt-get update -qq &>/dev/null
    $STD apt-get install -y jq &>/dev/null || {
    msg_error "Failed to install jq"
    return 1
    }
fi

jq is installed before NodeJS

[dannyellis]

jq is being called before the install_node_and_modules function
NODE_VERSION="22" NODE_MODULE="pnpm@$(curl -s https://raw.githubusercontent.com/docmost/docmost/main/package.json | jq -r '.packageManager | split("@")[1]')" install_node_and_modules

[flinthamm]

Wow, thank you for all your responses.

I'm still not fully up to speed with this scripting and this is the first time there has ever been an issue.

Sorry for the beginner question but can you confirm the quickest way to get this problem resolved and a working updatable container created?

[MickLesk]

right, its because they use an fixed pnpm version and we check it before nodejs install. Added dep in linked PR