Change Detection install fails #1985

Closed
opened 2026-02-05 03:12:32 +03:00 by OVERLORD · 8 comments
Owner

Originally created by @hgelpke on GitHub (Nov 12, 2025).

Have you read and understood the above guidelines?

yes

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

Change Detection

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

bash -c "$(curl -fsSL https://git.community-scripts.org/community-scripts/ProxmoxVE/raw/branch/main/ct/changedetection.sh)"

⚙️ What settings are you using?

  • Default Settings
  • Advanced Settings

🖥️ Which Linux distribution are you using?

Debian 12

📈 Which Proxmox version are you on?

bash -c "$(curl -fsSL https://git.community-scripts.org/community-scripts/ProxmoxVE/raw/branch/main/ct/changedetection.sh)"

📝 Provide a clear and concise description of the issue.

Install completes most steps but fails during the Browserless and Playwright setup inside an unprivileged LXC. The script exits with an error at line 159, then bubbles to line 1346.

🔄 Steps to reproduce the issue.

Run the install script on Proxmox 8 using default settings

Use an unprivileged Debian 12 LXC

Wait for the “Installing Browserless & Playwright” step

Paste the full error output (if available).

⠋ Installing Browserless & Playwright
[ERROR] in line 159: exit code 0: while executing command "$@" > /dev/null 2>&1

[ERROR] in line 1346: exit code 0: while executing command lxc-attach -n "$CTID" -- bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/install/${var_install}.sh)"

🖼️ Additional context (optional).


/ / / ____ _____ ____ ____ / __ _ / /___ / /() ____
/ / / __ / __ / __ \/ __ / _ \ / / / / _ / / _ / / / / __ / __
/ /
/ / / / /
/ / / / / /
/ / / / // / __/ // / // // / // / / / /
_
// //_,// //__, /_
/ /
/_/__/_/_/_//_// //
/
___/
⚙️ Using Default Settings on node homelab
🆔 Container ID: 102
🖥️ Operating System: debian (12)
📦 Container Type: Unprivileged
💾 Disk Size: 10 GB
🧠 CPU Cores: 2
🛠️ RAM Size: 2048 MiB
🚀 Creating a Change Detection LXC using the above default settings

✔️ Storage local (Free: 347.4GB Used: 15.4GB) [Template]
✔️ Storage local-zfs (Free: 347.4GB Used: 78.0GB) [Container]
✔️ Template debian-12-standard_12.7-1_amd64.tar.zst [local]
✔️ LXC Container 102 was successfully created.
✔️ Started LXC Container
✔️ Network in LXC is reachable (ping)
Extracting templates from packages: 100%
✔️ Customized LXC Container
✔️ Set up Container OS
✔️ Network Connected: 192.168.1.50 fd0a:3992:1802:c045:be24:11ff:fe3a:a3b9
✔️ IPv4 Internet Connected
✖️ IPv6 Internet Not Connected
✔️ Git DNS: github.com:(✔️ ) raw.githubusercontent.com:(✔️ ) api.github.com:(✔️ ) git.community-scripts.org:(✔️ )
✔️ Updated Container OS
✔️ Installed Dependencies
✔️ Setup Python3
✔️ Setup Node.js 24
✔️ Installed Change Detection
⠋ Installing Browserless & Playwright
[ERROR] in line 159: exit code 0: while executing command "$@" > /dev/null 2>&1

[ERROR] in line 1346: exit code 0: while executing command lxc-attach -n "$CTID" -- bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/install/${var_install}.sh)"

Originally created by @hgelpke on GitHub (Nov 12, 2025). ### ✅ Have you read and understood the above guidelines? yes ### 📜 What is the name of the script you are using? Change Detection ### 📂 What was the exact command used to execute the script? bash -c "$(curl -fsSL https://git.community-scripts.org/community-scripts/ProxmoxVE/raw/branch/main/ct/changedetection.sh)" ### ⚙️ What settings are you using? - [x] Default Settings - [ ] Advanced Settings ### 🖥️ Which Linux distribution are you using? Debian 12 ### 📈 Which Proxmox version are you on? bash -c "$(curl -fsSL https://git.community-scripts.org/community-scripts/ProxmoxVE/raw/branch/main/ct/changedetection.sh)" ### 📝 Provide a clear and concise description of the issue. Install completes most steps but fails during the Browserless and Playwright setup inside an unprivileged LXC. The script exits with an error at line 159, then bubbles to line 1346. ### 🔄 Steps to reproduce the issue. Run the install script on Proxmox 8 using default settings Use an unprivileged Debian 12 LXC Wait for the “Installing Browserless & Playwright” step ### ❌ Paste the full error output (if available). ⠋ Installing Browserless & Playwright [ERROR] in line 159: exit code 0: while executing command "$@" > /dev/null 2>&1 [ERROR] in line 1346: exit code 0: while executing command lxc-attach -n "$CTID" -- bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/install/${var_install}.sh)" ### 🖼️ Additional context (optional). ________ ____ __ __ _ / ____/ /_ ____ _____ ____ ____ / __ \___ / /____ _____/ /_(_)___ ____ / / / __ \/ __ `/ __ \/ __ `/ _ \ / / / / _ \/ __/ _ \/ ___/ __/ / __ \/ __ \ / /___/ / / / /_/ / / / / /_/ / __/ / /_/ / __/ /_/ __/ /__/ /_/ / /_/ / / / / \____/_/ /_/\__,_/_/ /_/\__, /\___/ /_____/\___/\__/\___/\___/\__/_/\____/_/ /_/ /____/ ⚙️ Using Default Settings on node homelab 🆔 Container ID: 102 🖥️ Operating System: debian (12) 📦 Container Type: Unprivileged 💾 Disk Size: 10 GB 🧠 CPU Cores: 2 🛠️ RAM Size: 2048 MiB 🚀 Creating a Change Detection LXC using the above default settings ✔️ Storage local (Free: 347.4GB Used: 15.4GB) [Template] ✔️ Storage local-zfs (Free: 347.4GB Used: 78.0GB) [Container] ✔️ Template debian-12-standard_12.7-1_amd64.tar.zst [local] ✔️ LXC Container 102 was successfully created. ✔️ Started LXC Container ✔️ Network in LXC is reachable (ping) Extracting templates from packages: 100% ✔️ Customized LXC Container ✔️ Set up Container OS ✔️ Network Connected: 192.168.1.50 fd0a:3992:1802:c045:be24:11ff:fe3a:a3b9 ✔️ IPv4 Internet Connected ✖️ IPv6 Internet Not Connected ✔️ Git DNS: github.com:(✔️ ) raw.githubusercontent.com:(✔️ ) api.github.com:(✔️ ) git.community-scripts.org:(✔️ ) ✔️ Updated Container OS ✔️ Installed Dependencies ✔️ Setup Python3 ✔️ Setup Node.js 24 ✔️ Installed Change Detection ⠋ Installing Browserless & Playwright [ERROR] in line 159: exit code 0: while executing command "$@" > /dev/null 2>&1 [ERROR] in line 1346: exit code 0: while executing command lxc-attach -n "$CTID" -- bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/install/${var_install}.sh)"
OVERLORD added the bug label 2026-02-05 03:12:32 +03:00
Author
Owner

@MickLesk commented on GitHub (Nov 12, 2025):

Verbose?

@MickLesk commented on GitHub (Nov 12, 2025): Verbose?
Author
Owner

@hgelpke commented on GitHub (Nov 12, 2025):

This is the fail point running with verbose

The following NEW packages will be installed:
microsoft-edge-stable
0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Need to get 180 MB of archives.
After this operation, 633 MB of additional disk space will be used.
Get:1 https://packages.microsoft.com/repos/edge stable/main amd64 microsoft-edge-stable amd64 142.0.3595.65-1 [180 MB]
Fetched 180 MB in 8s (23.7 MB/s)
Selecting previously unselected package microsoft-edge-stable.
(Reading database ... 50478 files and directories currently installed.)
Preparing to unpack .../microsoft-edge-stable_142.0.3595.65-1_amd64.deb ...
Unpacking microsoft-edge-stable (142.0.3595.65-1) ...
Setting up microsoft-edge-stable (142.0.3595.65-1) ...
update-alternatives: using /usr/bin/microsoft-edge-stable to provide /usr/bin/microsoft-edge (microsoft-edge) in auto mode
Processing triggers for mailcap (3.70+nmu1) ...
Processing triggers for man-db (2.11.2-2) ...

  • microsoft-edge-stable --version
    Microsoft Edge 142.0.3595.65

@browserless.io/browserless@2.38.2 build
npm run clean && npm run build:ts && npm run install:adblock && npm run build:schemas && npm run build:devtools && npm run build:openapi

@browserless.io/browserless@2.38.2 clean
node scripts/clean.js

@browserless.io/browserless@2.38.2 build:ts
tsc

@browserless.io/browserless@2.38.2 install:adblock
node scripts/install-adblock.js

@browserless.io/browserless@2.38.2 build:schemas
node scripts/build-schemas.js

Killed

[ERROR] in line 70: exit code 0: while executing command $STD npm run build --prefix /opt/browserless

[ERROR] in line 1346: exit code 0: while executing command lxc-attach -n "$CTID" -- bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/install/${var_install}.sh)"

@hgelpke commented on GitHub (Nov 12, 2025): This is the fail point running with verbose The following NEW packages will be installed: microsoft-edge-stable 0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded. Need to get 180 MB of archives. After this operation, 633 MB of additional disk space will be used. Get:1 https://packages.microsoft.com/repos/edge stable/main amd64 microsoft-edge-stable amd64 142.0.3595.65-1 [180 MB] Fetched 180 MB in 8s (23.7 MB/s) Selecting previously unselected package microsoft-edge-stable. (Reading database ... 50478 files and directories currently installed.) Preparing to unpack .../microsoft-edge-stable_142.0.3595.65-1_amd64.deb ... Unpacking microsoft-edge-stable (142.0.3595.65-1) ... Setting up microsoft-edge-stable (142.0.3595.65-1) ... update-alternatives: using /usr/bin/microsoft-edge-stable to provide /usr/bin/microsoft-edge (microsoft-edge) in auto mode Processing triggers for mailcap (3.70+nmu1) ... Processing triggers for man-db (2.11.2-2) ... + microsoft-edge-stable --version Microsoft Edge 142.0.3595.65 > @browserless.io/browserless@2.38.2 build > npm run clean && npm run build:ts && npm run install:adblock && npm run build:schemas && npm run build:devtools && npm run build:openapi > @browserless.io/browserless@2.38.2 clean > node scripts/clean.js > @browserless.io/browserless@2.38.2 build:ts > tsc > @browserless.io/browserless@2.38.2 install:adblock > node scripts/install-adblock.js > @browserless.io/browserless@2.38.2 build:schemas > node scripts/build-schemas.js Killed [ERROR] in line 70: exit code 0: while executing command $STD npm run build --prefix /opt/browserless [ERROR] in line 1346: exit code 0: while executing command lxc-attach -n "$CTID" -- bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/install/${var_install}.sh)"
Author
Owner

@MickLesk commented on GitHub (Nov 12, 2025):

Can you try with Double cpu/RAM? It Looks Like, that you get an OOM (Killed)

@MickLesk commented on GitHub (Nov 12, 2025): Can you try with Double cpu/RAM? It Looks Like, that you get an OOM (Killed)
Author
Owner

@hgelpke commented on GitHub (Nov 12, 2025):

Doubling the memory in advanced settings handled it.

@hgelpke commented on GitHub (Nov 12, 2025): Doubling the memory in advanced settings handled it.
Author
Owner

@tremor021 commented on GitHub (Nov 13, 2025):

Image

It works fine with default resources. I really dont know what to think here

@tremor021 commented on GitHub (Nov 13, 2025): <img width="802" height="719" alt="Image" src="https://github.com/user-attachments/assets/ba054e93-891d-4cda-b81c-4d8a5830f424" /> It works fine with default resources. I really dont know what to think here
Author
Owner

@Firecul commented on GitHub (Nov 20, 2025):

After getting the warning I came here to see what was up with the doubling of requirements. I'll be honest I don't think #9171 was needed, at least for an upgrade I didn't need anywhere near that level.
I have 31 watches atm fwiw.

Image

(Time base set to Hour Maximum)
Image

@Firecul commented on GitHub (Nov 20, 2025): After getting the warning I came here to see what was up with the doubling of requirements. I'll be honest I don't think #9171 was needed, at least for an upgrade I didn't need anywhere near that level. I have 31 watches atm fwiw. <img width="1089" height="335" alt="Image" src="https://github.com/user-attachments/assets/46e435cc-c71a-4216-96b3-31eb427508e4" /> (Time base set to Hour Maximum) <img width="1288" height="980" alt="Image" src="https://github.com/user-attachments/assets/55fd19fa-b159-4149-a84b-2ecf149c0538" />
Author
Owner

@MickLesk commented on GitHub (Nov 20, 2025):

And did you have the Same Hardware then Others? If some Users get an OOM, should we discard this Issues specially for you?

@MickLesk commented on GitHub (Nov 20, 2025): And did you have the Same Hardware then Others? If some Users get an OOM, should we discard this Issues specially for you?
Author
Owner

@Firecul commented on GitHub (Nov 20, 2025):

And did you have the Same Hardware then Others? If some Users get an OOM, should we discard this Issues specially for you?

I'm not sure what brand of memory I have but I don't think 2GB of it is any better than 2GB of anyone elses since it's in an old Elitedesk. Although here is the spec if that wasn't a sarcastic question.

OS: Proxmox VE 8.4.14 x86_64 
Host: HP EliteDesk 800 G5 Desktop Mini SBKPF 
Kernel: 6.8.12-11-pve 
Uptime: 91 days, 16 hours, 59 mins 
Packages: 861 (dpkg) 
Shell: bash 5.2.15 
Terminal: /dev/pts/0 
CPU: Intel i5-8500T (6) @ 800MHz 
GPU: Intel CoffeeLake-S GT2 [UHD Graphics 630] 
Memory: 3692MiB / 7275MiB

I was giving input not claiming everything should be changed to accommodate me.

@Firecul commented on GitHub (Nov 20, 2025): > And did you have the Same Hardware then Others? If some Users get an OOM, should we discard this Issues specially for you? I'm not sure what brand of memory I have but I don't think 2GB of it is any better than 2GB of anyone elses since it's in an old Elitedesk. Although here is the spec if that wasn't a sarcastic question. ``` OS: Proxmox VE 8.4.14 x86_64 Host: HP EliteDesk 800 G5 Desktop Mini SBKPF Kernel: 6.8.12-11-pve Uptime: 91 days, 16 hours, 59 mins Packages: 861 (dpkg) Shell: bash 5.2.15 Terminal: /dev/pts/0 CPU: Intel i5-8500T (6) @ 800MHz GPU: Intel CoffeeLake-S GT2 [UHD Graphics 630] Memory: 3692MiB / 7275MiB ``` I was giving input not claiming everything should be changed to accommodate me.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/ProxmoxVE#1985