wger install fails #1755

Closed
opened 2026-02-05 02:11:30 +03:00 by OVERLORD · 2 comments
Owner

Originally created by @DonLocke on GitHub (Oct 9, 2025).

Have you read and understood the above guidelines?

yes

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

wger

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

bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/wger.sh)"

⚙️ What settings are you using?

  • Default Settings
  • Advanced Settings

🖥️ Which Linux distribution are you using?

Debian 13

📈 Which Proxmox version are you on?

9.0.10

📝 Provide a clear and concise description of the issue.

The wger script is failing during installation of pip requirements, verbose output shown below.

🔄 Steps to reproduce the issue.

Run wger install script.

Paste the full error output (if available).

Attempting uninstall: packaging
Found existing installation: packaging 25.0
━━━━━━━━━━━━╺━━━━━━━━━━━━━━━━━━━━━━━━━━━ 25/82 [pillow]error: uninstall-no-record-file

× Cannot uninstall packaging 25.0
╰─> The package's contents are unknown: no RECORD file was found for packaging.

hint: The package was installed by debian. You should check if it can uninstall the package.

[ERROR] in line 45: exit code 0: while executing command $STD pip install -r requirements_prod.txt

[ERROR] in line 1345: 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).

I did verify that all host packages are up to date including pve-container (6.0.13).

Originally created by @DonLocke on GitHub (Oct 9, 2025). ### ✅ Have you read and understood the above guidelines? yes ### 📜 What is the name of the script you are using? wger ### 📂 What was the exact command used to execute the script? bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/wger.sh)" ### ⚙️ What settings are you using? - [ ] Default Settings - [x] Advanced Settings ### 🖥️ Which Linux distribution are you using? Debian 13 ### 📈 Which Proxmox version are you on? 9.0.10 ### 📝 Provide a clear and concise description of the issue. The wger script is failing during installation of pip requirements, verbose output shown below. ### 🔄 Steps to reproduce the issue. Run wger install script. ### ❌ Paste the full error output (if available). Attempting uninstall: packaging Found existing installation: packaging 25.0 ━━━━━━━━━━━━╺━━━━━━━━━━━━━━━━━━━━━━━━━━━ 25/82 [pillow]error: uninstall-no-record-file × Cannot uninstall packaging 25.0 ╰─> The package's contents are unknown: no RECORD file was found for packaging. hint: The package was installed by debian. You should check if it can uninstall the package. [ERROR] in line 45: exit code 0: while executing command $STD pip install -r requirements_prod.txt [ERROR] in line 1345: 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). I did verify that all host packages are up to date including pve-container (6.0.13).
OVERLORD added the bug label 2026-02-05 02:11:30 +03:00
Author
Owner

@DonLocke commented on GitHub (Oct 9, 2025):

I was able to get it to work by:

  1. manually running the failed command with an ignore installed flag in the container it created
    pip install -r requirements_prod.txt --ignore-installed

  2. followed by exeucting the install portion of the script by running inside the container.
    bash -c "$(curl -fsSl https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/install/wger-install.sh)"

Maybe that flag needs to be added to the script?

@DonLocke commented on GitHub (Oct 9, 2025): I was able to get it to work by: 1) manually running the failed command with an ignore installed flag in the container it created `pip install -r requirements_prod.txt --ignore-installed` 2) followed by exeucting the install portion of the script by running inside the container. `bash -c "$(curl -fsSl https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/install/wger-install.sh)"` Maybe that flag needs to be added to the script?
Author
Owner

@axela74 commented on GitHub (Oct 9, 2025):

I've the same error. I tried to run pip install with --ignore-installed but when I run:
bash -c "$(curl -fsSl https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/install/wger-install.sh)"
I get many errors (msg_ok: command not found, sed: can't read /home/wger/src/settings.py: No such file or directory
bash: line 50: wger: command not found) and than on apache I've this error:

Python home /home/wger is not accessible. Python interpreter may not be able to be initialized correctly. Verify the supplied path and access permissions on the directory.
[Thu Oct 09 22:53:11.899612 2025] [wsgi:crit] [pid 6451:tid 6451] mod_wsgi (pid=6451): Initializing Python failed: Failed to import encodings module
[Thu Oct 09 22:53:12.885824 2025] [core:notice] [pid 6190:tid 6190] AH00052: child pid 6451 exit signal Segmentation fault (11)

@axela74 commented on GitHub (Oct 9, 2025): I've the same error. I tried to run pip install with --ignore-installed but when I run: `bash -c "$(curl -fsSl https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/install/wger-install.sh)"` I get many errors (msg_ok: command not found, sed: can't read /home/wger/src/settings.py: No such file or directory bash: line 50: wger: command not found) and than on apache I've this error: Python home /home/wger is not accessible. Python interpreter may not be able to be initialized correctly. Verify the supplied path and access permissions on the directory. [Thu Oct 09 22:53:11.899612 2025] [wsgi:crit] [pid 6451:tid 6451] mod_wsgi (pid=6451): Initializing Python failed: Failed to import encodings module [Thu Oct 09 22:53:12.885824 2025] [core:notice] [pid 6190:tid 6190] AH00052: child pid 6451 exit signal Segmentation fault (11)
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/ProxmoxVE#1755