“unsupported debian version” / Container Creation Failures on PVE 8 & 9 #8126
Replies: 6 comments 31 replies
-
|
apt update This solution has resulted in Proxmox no longer starting up. Previously: And all this just because I wanted to test Trilium Notes and couldn't install Trilium Notes due to the Debian error message. |
Beta Was this translation helpful? Give feedback.
-
|
How should I do it? |
Beta Was this translation helpful? Give feedback.
-
|
This cannot be the cause, but rather other system components, e.g., a broken kernel or defective Grub. Pve-Container is just software, like Firefox, for example. Connect the PC to a monitor and see why Grub is not loading. |
Beta Was this translation helpful? Give feedback.
-
|
After updating directly on the host, I can fortunately access Proxmox from outside again. However, it is still 5.3.3 and the error message appears. And there are no more updates available. |
Beta Was this translation helpful? Give feedback.
-
|
Your Bad, all other working fine. Then Update your complete Proxmox |
Beta Was this translation helpful? Give feedback.
-
It's sorted. Thanks In the description for “PVE Post Install,” I would also recommend mentioning that the new repo format deb822 is being automatically configured, because I had to struggle with it manually before. Didn't know that the script offers to configure it automatically now. |
Beta Was this translation helpful? Give feedback.
-
|
Everything is updated and upgraded in my system and I'm still getting the same error (from Example 2)
|
Beta Was this translation helpful? Give feedback.
-
|
That container has been successfully created. |
Beta Was this translation helpful? Give feedback.
-
|
Huch, thats deb12. Moment. Try again in 5min |
Beta Was this translation helpful? Give feedback.
-
|
This time deb13 has been successfully installed. |
Beta Was this translation helpful? Give feedback.
-
|
Then it Exit currently with an Exit Code that Not handled in this core. Why? I have no idea what the difference is between your system and thousands of others. |
Beta Was this translation helpful? Give feedback.
-
Thank you MickLesk. It turns out that when I had previously disabled the Enterprise versions of the pve and ceph-squid repositories (which were preventing updates), I didn't have all the repositories I needed to to a proper update/upgrade to proxmox. Once I added the no-subscription versions of the pve and ceph-squid repositories, I was able to update and upgrade and then the helper script was able to run successfully. |
Beta Was this translation helpful? Give feedback.
-
|
I did everything listed under solutions but I still have the error from Example 2 (using n8n script as an example): I also ran the script in verbose mode, but got no additional info or clue. I did try the solutions: pve-container version seems up-to date to me: I also ran |
Beta Was this translation helpful? Give feedback.
-
|
Your packages are corrupt. There are Missing Sources. So you never get an actual system. Idk why you have removed f.e. the no-subscription and so on. Check your system First. |
Beta Was this translation helpful? Give feedback.
-
|
http://download.proxmox.com/debian/pve trixie InRelease is missing f.e. |
Beta Was this translation helpful? Give feedback.
-
|
yeah my bad, I think I forgot to add that source in the first place😔. It's working now. Thanks |
Beta Was this translation helpful? Give feedback.
-
Please guide me how to fix it, i have the same error as you |
Beta Was this translation helpful? Give feedback.
-
|
Just came to chime in that i had this issue, it failed (great job including this link), then after updating it still failed. I had to delete the debian image and then it worked without issue. |
Beta Was this translation helpful? Give feedback.
-
|
@MickLesk All due respect but there's a pretty gnarly validation gap in this script in the fail cause of a download getting interrupted after 1mb that has nothing to do with the RCA y'all posted above. Proposing users updating their Would be pretty trivial to detect the pve-container version and handle the errors appropriately. Would you like me to submit a PR with a proposed fix? ETA: I realize being a maintainer can be very thankless at times, so please accept my gratitude for all that you do. Let me know if I can help! Rough example: # Fail fast if compatibility issue detected
PVE_CONTAINER_VER=$(dpkg-query -W -f='${Version}' pve-container 2>/dev/null | cut -d. -f1-2)
if [[ "$PVE_CONTAINER_VER" =~ ^[89]\. ]] && [[ "$TEMPLATE" =~ debian-13 ]]; then
msg_error "Known issue: Proxmox $PVE_CONTAINER_VER with Debian 13.x templates. Suggested fix is updating `pve-container`. Please check https://github.com/community-scripts/ProxmoxVE/discussions/8126"
exit 209
fi
if ! pct create "$CTID" "${TEMPLATE_STORAGE}:vztmpl/${TEMPLATE}" "${PCT_OPTIONS[@]}" &>/dev/null; then
msg_error "Container creation failed. Checking if template is corrupted or incomplete."
if [[ ! -s "$TEMPLATE_PATH" || "$(stat -c%s "$TEMPLATE_PATH")" -lt 1000000 ]]; then
msg_error "Template file too small or missing – re-downloading."
rm -f "$TEMPLATE_PATH"
elif ! zstdcat "$TEMPLATE_PATH" | tar -tf - &>/dev/null; then
msg_error "Template appears to be corrupted – re-downloading."
rm -f "$TEMPLATE_PATH"
else
# Example error for handling fail cause of template exceeding 1Mb but failing to fully download
msg_error "Container creation failed. This may be due to an interrupted download during the previous download of the template. Please try deleting cache for template in ${TEMPLATE_PATH} and trying again."
exit <some nzec>
fi
# Retry download
for attempt in {1..3}; do
msg_info "Attempt $attempt: Re-downloading template..."
if timeout 120 pveam download "$TEMPLATE_STORAGE" "$TEMPLATE" >/dev/null; then
msg_ok "Template re-download successful."
break
fi
if [ "$attempt" -eq 3 ]; then
msg_error "Three failed attempts. Aborting."
exit 208
fi
sleep $((attempt * 5))
done
sleep 1 # I/O-Sync-Delay
msg_ok "Re-downloaded LXC Template"
fi
if ! pct list | awk '{print $1}' | grep -qx "$CTID"; then
msg_error "Container ID $CTID not listed in 'pct list' – unexpected failure."
exit 215
fi |
Beta Was this translation helpful? Give feedback.
-
|
That has nothing To-Do with the Download. Proxmox give the Output "unsupported" Version. If unsupported -> pct create fails. Or did you mean this in General? You can take a Look into build.func from our VED, there are many many fixes for this and other Fürther Issues. If you see anything more to fix, feel free to make an PR with some improvements. (VED doesnt have "create_lxc" its implemented in build.func) |
Beta Was this translation helpful? Give feedback.
-
|
Yeah, I understand - there's two fail states that are being lumped together, the unsupported version and if a download fails but exceeds 1Mb. Just proposing that they be handled separately as the solutions are distinctly different. Will push up a PR and go from there. Also it might be prudent to warn people that |
Beta Was this translation helpful? Give feedback.
-
|
I always assumed that you know what you're doing when you're updating the software on your machine. Clearly some user effort is needed in these matters, we can't be assuming that user just sat in front of his PVE host for the first time in his life... |
Beta Was this translation helpful? Give feedback.
-
|
@tremor021 Thanks for sharing. I don't disagree necessarily, but what level of effort is expected from the user here? The error handling and proscribed solution is objectively wrong for the fail case. Perhaps that wasn't evident? |
Beta Was this translation helpful? Give feedback.
-
|
For those struggling with this. I believe the solution needs to be updated or at least a disclaimer needs to be added. I'm new to proxmox so had to do a bit of googling around to figure this out. Indeed, if like me (and I assume others facing the same problem) you are not using the subscription, then you need to disable the subscription based repositories. As soon as you do this, apt update / apt upgrade will fetch the pve-container 6.0.13 and then the scripts will work. FYI: @MickLesk |
Beta Was this translation helpful? Give feedback.
-
|
@teuteuguy your comment helped me fix the issue. I'm also new to proxmox and was struggling to implement the solution. Thanks!! |
Beta Was this translation helpful? Give feedback.
-
|
That ive written above ^^ |
Beta Was this translation helpful? Give feedback.
-
|
@MickLesk You absolutely right! I overlooked the first line in solution 3. Since I'm new to Proxmox, I do most things through the UI. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
🧩 Proxmox VE — “unsupported debian version '13.1'” Error During LXC Creation
We receive multiple reports every day regarding this issue.
Please note:
➡️ This is not caused by the Community Scripts.
➡️ It’s a known Proxmox VE bug, specifically within the
pve-containerpackage.Examples:
#8095 · #8106 · #8058 · #8085
🧠 Problem
When creating a container (e.g., via a Community Script), you may see:
or
These messages are not script errors — they come directly from the Proxmox VE LXC subsystem (
pve-container).⚙️ Root Cause
Older versions of
pve-containerincorrectly flag Debian 13.1 (“Trixie”) as unsupported.Affected versions:
🛠 Solutions
🩵 1. Solution – Full System Upgrade
Recommended if your system hasn’t been updated recently.
Then verify:
For PVE 8 → latest is 5.3.3
For PVE 9 → latest is 6.0.13
💚 2. Solution – Update Only
pve-containerIf your system is otherwise current:
Check version afterwards:
🧩 3. Solution – Verify Repository Configuration
Many users disable Enterprise repos but forget to add the no-subscription ones — leaving APT with incomplete sources.
Check your repo file:
For PVE 9 (Trixie):
For PVE 8 (Bookworm):
Then run:
This ensures you receive the correct
pve-container(5.3.3 or 6.0.13).Edit:
Find:
Change to:
Then restart services:
✅ Summary
unsupported debian version '13.1'pve-container/var/lib/vz📢 Note
Because this issue is reported multiple times daily, this post serves as the official reference.
New reports about this Proxmox bug will be closed with a link to this document.
🧭 Conclusion
pve-containerupdatesBeta Was this translation helpful? Give feedback.
All reactions