“unsupported debian version” / Container Creation Failures on PVE 8 & 9 #8126
Pinned
MickLesk
announced in
Announcements
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
We are receiving multiple reports per day (5 or more) about this issue — but please note:
➡️ This is not caused by the Community Scripts.
➡️ It’s a known Proxmox bug related to the
pve-container
package.Examples: #8095 #8106 #8058 #8085
🧩 Problem Description
When you try to create a container using one of the Community Scripts, you may see one of the following errors:
Example 1
Example 2
Example 3
These messages may look like script errors — but they actually originate from Proxmox VE’s own LXC subsystem (
pve-container
).🧠 Root Cause
Proxmox has a known bug in recent versions of the
pve-container
package.It incorrectly marks newer Debian releases (e.g. 13.1 “Trixie”) as unsupported when creating a new container.
This affects:
🛠️ Solution
You must update your Proxmox host packages, especially
pve-container
.Run the following command on your Proxmox node (not inside the container):
After upgrading, verify the version:
Make sure it’s the latest available for your PVE version.
Then re-run the script — the container will be created successfully.
✅ Summary
unsupported debian version '13.1'
pve-container
packageapt install --only-upgrade pve-container -y
pveam update
/var/lib/vz
space🧭 TL;DR
📢 Important Announcement
Because we receive at least five identical Issues every day, this guide will serve as our official reference.
New Issues about this Proxmox bug will be closed immediately with a link to this document.
In the coming days and weeks, we’ll begin upgrading all Debian 12 scripts (where possible) to Debian 13 to ensure long-term compatibility and fewer false error reports.
Thank you for your understanding and support. 💙
— The Community Scripts Team
Beta Was this translation helpful? Give feedback.
All reactions