starred/ProxmoxVE
1
0
Fork 0
mirror of https://github.com/community-scripts/ProxmoxVE.git synced 2026-02-05 00:29:55 +03:00
Code Issues 12 Packages Projects Releases 10 Wiki Activity

NetBox LXC update fails due to removed Python 3.11 support #2375

New Issue
Closed
opened 2026-02-05 04:39:23 +03:00 by OVERLORD · 4 comments
OVERLORD commented 2026-02-05 04:39:23 +03:00
Owner
Copy Link

Originally created by @Ionic97 on GitHub (Jan 24, 2026).

✅ Have you read and understood the above guidelines?

yes

🔎 Did you run the script with verbose mode enabled?

Yes, verbose mode was enabled and the output is included below

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

NetBox

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

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

⚙️ What settings are you using?

  • Default Settings
  • Advanced Settings

🖥️ Which Linux distribution are you using?

Debian 12

📈 Which Proxmox version are you on?

9.1.4

📝 Provide a clear and concise description of the issue.

NetBox has removed support for Python 3.11 from version 4.5.0 onward as is noted in their release notes: https://github.com/netbox-community/netbox/releases
The updater does not try to update the dependency, thus the installation fails.

I tried performing the Debian 13 upgrade as documented here (https://github.com/community-scripts/ProxmoxVE/discussions/7489) but failed to do so successfully.

🔄 Steps to reproduce the issue.

  • have installed NetBox via Community Script prior to v4.5.0
  • try to update via the installation script or update command

❌ Paste the full error output (if available).

You are installing (or upgrading to) NetBox version 4.5.1
--------------------------------------------------------------------
ERROR: Unsupported Python version: Python 3.11.2. NetBox requires
Python 3.12 or later. To specify an alternate Python executable, set
the PYTHON environment variable. For example:

  sudo PYTHON=/usr/bin/python3.12 ./upgrade.sh

To show your current Python version: python3 -V
--------------------------------------------------------------------
  ✖️   in line 59: exit code 1 (General error / Operation not permitted): while executing command  /opt/netbox/upgrade.sh

🖼️ Additional context (optional).

No response

Originally created by @Ionic97 on GitHub (Jan 24, 2026). ### ✅ Have you read and understood the above guidelines? yes ### 🔎 Did you run the script with verbose mode enabled? Yes, verbose mode was enabled and the output is included below ### 📜 What is the name of the script you are using? NetBox ### 📂 What was the exact command used to execute the script? bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/netbox.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? 9.1.4 ### 📝 Provide a clear and concise description of the issue. NetBox has removed support for Python 3.11 from version 4.5.0 onward as is noted in their release notes: https://github.com/netbox-community/netbox/releases The updater does not try to update the dependency, thus the installation fails. I tried performing the Debian 13 upgrade as documented here (https://github.com/community-scripts/ProxmoxVE/discussions/7489) but failed to do so successfully. ### 🔄 Steps to reproduce the issue. - have installed NetBox via Community Script prior to v4.5.0 - try to update via the installation script or update command ### ❌ Paste the full error output (if available). ``` You are installing (or upgrading to) NetBox version 4.5.1 -------------------------------------------------------------------- ERROR: Unsupported Python version: Python 3.11.2. NetBox requires Python 3.12 or later. To specify an alternate Python executable, set the PYTHON environment variable. For example: sudo PYTHON=/usr/bin/python3.12 ./upgrade.sh To show your current Python version: python3 -V -------------------------------------------------------------------- ✖️ in line 59: exit code 1 (General error / Operation not permitted): while executing command /opt/netbox/upgrade.sh ``` ### 🖼️ Additional context (optional). _No response_
OVERLORD added the not a script issue label 2026-02-05 04:39:23 +03:00
OVERLORD commented 2026-02-05 04:39:28 +03:00
Author
Owner
Copy Link

@vhsdream commented on GitHub (Jan 24, 2026):

Is this only happening because you're using a Debian 12 LXC? If so I'd say it's not a script issue since the script now uses Trixie and Trixie will have Python 3.12+.

I suggest attempting the Bookworm > Trixie upgrade again and asking for help in that thread.

That being said, it looks like the Netbox scripts in general need to be updated to current standards.

@vhsdream commented on GitHub (Jan 24, 2026): Is this only happening because you're using a Debian 12 LXC? If so I'd say it's not a script issue since the script now uses Trixie and Trixie will have Python 3.12+. I suggest attempting the Bookworm > Trixie upgrade again and asking for help in that thread. That being said, it looks like the Netbox scripts in general need to be updated to current standards.
OVERLORD commented 2026-02-05 04:39:32 +03:00
Author
Owner
Copy Link

@Ionic97 commented on GitHub (Jan 24, 2026):

In that case the script should cancel and not proceed with the update and mention that 12 is not supported anymore. The way it currently works, the script breaks the application, due to the failed update which leaves me to restore from a backup or snapshot. I would therefore still consider this a script issue of some kind.

@Ionic97 commented on GitHub (Jan 24, 2026): In that case the script should cancel and not proceed with the update and mention that 12 is not supported anymore. The way it currently works, the script breaks the application, due to the failed update which leaves me to restore from a backup or snapshot. I would therefore still consider this a script issue of some kind.
OVERLORD commented 2026-02-05 04:39:37 +03:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Jan 25, 2026):

an correct apt upgrade to debian 13 should update every python dependency.

Ive tested it atm with an default debian 12 lxc and upgraded to deb 13
python3 before: Python 3.11.2
python3 after: Python 3.13.5

@MickLesk commented on GitHub (Jan 25, 2026): an correct apt upgrade to debian 13 should update every python dependency. Ive tested it atm with an default debian 12 lxc and upgraded to deb 13 python3 before: Python 3.11.2 python3 after: Python 3.13.5
OVERLORD commented 2026-02-05 04:39:40 +03:00
Author
Owner
Copy Link

@tremor021 commented on GitHub (Jan 25, 2026):

In that case the script should cancel and not proceed with the update and mention that 12 is not supported anymore. The way it currently works, the script breaks the application, due to the failed update which leaves me to restore from a backup or snapshot. I would therefore still consider this a script issue of some kind.

Update script does what its supposed to do. It can't know when will your app decide to not support Python 3.11 any more...
You've been given correct steps to proceed by @MickLesk
Upgrade your container to Debian 13 and it will continue to work fine

@tremor021 commented on GitHub (Jan 25, 2026): > In that case the script should cancel and not proceed with the update and mention that 12 is not supported anymore. The way it currently works, the script breaks the application, due to the failed update which leaves me to restore from a backup or snapshot. I would therefore still consider this a script issue of some kind. Update script does what its supposed to do. It can't know when will your app decide to not support Python 3.11 any more... You've been given correct steps to proceed by @MickLesk Upgrade your container to Debian 13 and it will continue to work fine
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Implemented in VED waiting push to Main
breaking change
bug
bug
bugfix
deferred
delete script
dependencies
enhancement
external
feature
github
help wanted
in project pipeline
invalid
investigation
json
maintenance
needs triage
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
🛑 Failure to comply with the guidelines
No Label not a script issue
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
OVERLORD
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/ProxmoxVE#2375
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?