Debian 13 Upgrade for existing LXC #7489
Replies: 39 comments 89 replies
|
Here are my findings from my server, all of these apps are in separate LXCs.. These apps (LXCs) have been pre-built via the community script (These are not fresh installs), and run fine after updating from Debian 12 to Debian 13 after following the commands above:
Note: Except for Notifarr, the update script run successfully on all LXCs, however I didn't actually have any apps that required updating so this has not been fully tested. These apps (LXCs) were NOT pre-built via community scripts (as I prefer the beta version) but still run fine on Debian 13: These apps (LXCs) have been pre-built via the community script (These are not fresh installs) and do not work when updating to Debian 13: For future reference, Unpackerr from the project board also runs fine on Debian 13. I hope this helps. Thanks. |
|
these works for me (some extensively tested more than others):
NOT working:
|
|
These do not work for me after Debian 13 upgrade inside the LXC:
phpipam and WallOS seem to be Apache2/PHP module issues causing Apache2 to not load. Bar-Assistant will not connect to the API after upgrade (checked IPs in config, all correct) |
|
@jonnewman85 check out the linked github issue, it contains a fix for wallos. |
|
LCX upgrade to Debian 13 worked OK:
|
couldn't get it to work with my paperless-ngx container. Prompted me to upgrade postgresql - i ran it with and without the upgrade, still not working. |
|
Grafana update script expects "/etc/apt/sources.list.d/grafana.list" not "/etc/apt/sources.list.d/grafana.sources" as debian 13 source |
|
So I know we've established that the Homepage LXC is safe to update, but I've been running it for so long I forgot it was on Bullseye. I was able to upgrade to Bookworm, then reboot and upgrade to Trixie just fine. |
|
Heimdall-Dashboard no longer works when I try to load the webpage. |
|
@ksj9877us can you add some sort of logs or something like that? |
|
I managed to make Heimdall work: |
|
Thanks for this. It didn't work after running the additional commands above, but I did find the reason in the logs. Dec 01 09:47:07 heimdall-dashboard systemd[1]: Started heimdall.service - Heimdall. After installing php-zip, it works correctly. |
|
Technitium DNS works perfect with this script. Updated to Trixie without any problem |
This comment was marked as duplicate.
This comment was marked as duplicate.
|
Zabbix seems to work (no postgresql upgrade). I need to install the PostgreSQL database module for PHP package after all to recover database connection After rebooting, the update command shows ⏳ Stopping ServicesFailed to stop zabbix-agent.service: Unit zabbix-agent.service not loaded. [ERROR] in line 45: exit code 0: while executing command systemctl stop zabbix-server $AGENT_SERVICE |
|
@kriss0707 all php modules need to be reinstalled view here on how to do this: #7332 |
@CrazyWolf13 Seems nothing else than the mentioned I just updated my Debian 12 Zabbix container to Debian 13 with the procedure outlined above, then installed php-pgsql as mentioned by @kriss0707, and all is good. Unless I misunderstand something, looking at https://github.com/community-scripts/ProxmoxVE/blob/main/install/zabbix-install.sh line 26 I find: Now trying to reinstall those two PHP modules zabbix-frontend-php and php8.4-pgsql shows the following: Or did you refer to PHP modules in general, not for the Zabbix helper script specifically? |
|
@CrazyWolf13 I did. But seems we are going in circles. According to @kriss0707 s0707 only |
|
these are working fine for me:
I do get the "Policy will reject signature within a year" message for: Later edit: Vaultwarden has been fine too |
|
@summoningpixels You should be fine to remove this: Can you send the outputs of the following:
And also can you remove all the files related to azul zulu inside of /etc/apt/sources.list.d/ directory? Then run apt update again and ensure with |
|
@CrazyWolf13 that did it, everything is clean now. |
|
@summoningpixels awesome! Can you share what files you had to remove from the azul zulu repo? So we can maybe do this via script? |
|
@CrazyWolf13 it was |
|
I have not been able to get WireGuard working after upgrading. Was there something specific you had to do or was it working immediately? |
|
sabnzbd LXC Debian12 > 13 Upgrade it failed to start the sabnzbd systemd service due to i had to remove the virtual environment EDIT - Correct solution over here: #7489 (reply in thread) . activate Venv install requirements and close the Venv after restarting the sabnzbd systemd service, sabnzbd should run again |
|
sabnzbd doesnt Work with python3 venv, so you Break the next Update sabnzbd Runs with uv |
|
how about that to rebuild venv? is that good for future updates? |
|
Yeah uv venv /opt/sabnzbd/venv |
|
Nginx Proxy Manager works perfect with this script. Updated to Trixie without any problem |
|
The update to Debian 13 is not working for After update service is not accessible |
|
The update works for Resilio Sync LXC. No issue The update works for Gotify LXC. No issue The update works for Vaultwarden LXC. No issue The update works for Adguardhome LXC (+ Stork + isc-kea-dhcp installed in the LXC). No issue (migration of postgresql from 15 to 17). thanks for this guidance |
|
I tried upgrading Te update commands: After reboot command the LXC don't start |
|
No, i have the Proxmox v9.0.11 |
|
That say nothing. "pve-container" is relevant |
|
And you see Output If you start the Container with pct. Then you see whats broken |
|
There were packages to update in proxmox, now I managed to update 
|
|
👍 |
This comment was marked as off-topic.
This comment was marked as off-topic.
|
Updated a bunch of containers using this script and most worked great. A problematic culprit that has already been mentioned is Changedetection... and a couple that haven't been mentioned are Bazarr and Privatebin. About to troubleshoot them now. |
|
Successfully updated the following:
Failed:
|
|
Thanks, please run in advanced mode to share details. Interesting thing in forgejo, are you sure this is just not some quirk of the console? sometimes it behaves a bit weird. |
|
It definitely has to do with nesting, I've tested it rolling back to a Debian 12 version (no nesting) and re-upgrading. If disabled I am not able to enter the console. It took me days before I ever noticed because I generally do not use the console because of its quirks, I noticed in the journal the console-getty.service was failing (among others) on boot. I monitored startup from an ssh session, enabling nesting clears the console-getty.service failure. After a bit of research it seems to not be an uncommon thing with lxc., at least on Debian/Ubuntu. Nesting is enabled by default in the helper-scripts, I disabled it during install because I didn't think I'd need it. I've checked a couple other Debian 13 lxc and the pve webgui console does not work when nesting disabled. I should clarify this is a brand new install, installed using the Debian 12 script using advanced settings, backed up the lxc, and then upgraded. |
|
i have been having super weird ssh issues since the upgrade, i have nesting enabled fyi. i think it should be pretty easy to create like a tar in place like the host backup and then scp the tar out, do a clean install and then copy it back over before extracting it inplace as a reset. ill get around to this sooner or later, but if someone else could do the work for me id love you forever wait a minute im going to try to rerun this https://github.com/community-scripts/ProxmoxVE/blob/main/install/forgejo-install.sh#L21-L27 with the notes from #7485 - wish me luck man this root issue is bad, i cant even make a backup, neither of the 3 ways INFO: starting new backup job: vzdump 103 --notes-template '{{guestname}}-pray' --node skylake1 --compress zstd --remove 0 --storage local --notification-mode notification-system --mode snapshot
INFO: filesystem type on dumpdir is 'zfs' -using /var/tmp/vzdumptmp1759312_103 for temporary files
INFO: Starting Backup of VM 103 (lxc)
INFO: Backup started at 2026-01-03 23:53:53
INFO: status = running
INFO: CT Name: forgejo
INFO: including mount point rootfs ('/') in backup
INFO: backup mode: snapshot
INFO: ionice priority: 7
INFO: create storage snapshot 'vzdump'
INFO: creating vzdump archive '/var/lib/vz/dump/vzdump-lxc-103-2026_01_03-23_53_53.tar.zst'
INFO: tar: ./root: Cannot open: Permission denied
INFO: tar: ./etc/credstore.encrypted: Cannot open: Permission denied
INFO: tar: ./etc/credstore: Cannot open: Permission denied
INFO: tar: ./var/cache/private: Cannot open: Permission denied
INFO: tar: ./var/spool/cron/crontabs: Cannot open: Permission denied
INFO: tar: ./var/lib/private: Cannot open: Permission denied
INFO: tar: ./var/lib/docker: Cannot open: Permission denied
INFO: tar: ./var/log/private: Cannot open: Permission denied
INFO: Total bytes written: 6373457920 (6.0GiB, 77MiB/s)
INFO: tar: Exiting with failure status due to previous errors
INFO: cleanup temporary 'vzdump' snapshot
ERROR: Backup of VM 103 failed - command 'set -o pipefail && lxc-usernsexec -m u:0:100000:65536 -m g:0:100000:65536 -- tar cpf - --totals --one-file-system -p --sparse --numeric-owner --acls --xattrs '--xattrs-include=user.*' '--xattrs-include=security.capability' '--warning=no-file-ignored' '--warning=no-xattr-write' --one-file-system '--warning=no-file-ignored' '--directory=/var/tmp/vzdumptmp1759312_103' ./etc/vzdump/pct.conf ./etc/vzdump/pct.fw '--directory=/mnt/vzsnap0' --no-anchored '--exclude=lost+found' --anchored '--exclude=./tmp/?*' '--exclude=./var/tmp/?*' '--exclude=./var/run/?*.pid' ./ | zstd '--threads=1' >/var/lib/vz/dump/vzdump-lxc-103-2026_01_03-23_53_53.tar.dat' failed: exit code 2
INFO: Failed at 2026-01-03 23:55:14
INFO: Backup job finished with errors
INFO: notified via target `mail-to-root`
TASK ERROR: job errors
INFO: starting new backup job: vzdump 103 --notes-template '{{guestname}}-pray' --node skylake1 --compress zstd --remove 0 --mode suspend --storage local --notification-mode notification-system
INFO: filesystem type on dumpdir is 'zfs' -using /var/tmp/vzdumptmp1764585_103 for temporary files
INFO: Starting Backup of VM 103 (lxc)
INFO: Backup started at 2026-01-03 23:57:36
INFO: status = running
INFO: backup mode: suspend
INFO: ionice priority: 7
INFO: CT Name: forgejo
INFO: including mount point rootfs ('/') in backup
INFO: starting first sync /proc/1677555/root/ to /var/tmp/vzdumptmp1764585_103
INFO: first sync finished - transferred 10.00G bytes in 106s
INFO: suspending guest
INFO: starting final sync /proc/1677555/root/ to /var/tmp/vzdumptmp1764585_103
INFO: final sync finished - transferred 29.47M bytes in 6s
INFO: resuming guest
INFO: guest is online again after 6 seconds
INFO: creating vzdump archive '/var/lib/vz/dump/vzdump-lxc-103-2026_01_03-23_57_36.tar.zst'
INFO: tar: ./root: Cannot open: Permission denied
INFO: tar: ./var/log/private: Cannot open: Permission denied
INFO: tar: ./var/lib/docker: Cannot open: Permission denied
INFO: tar: ./var/lib/private: Cannot open: Permission denied
INFO: tar: ./var/spool/cron/crontabs: Cannot open: Permission denied
INFO: tar: ./var/cache/private: Cannot open: Permission denied
INFO: tar: ./etc/credstore.encrypted: Cannot open: Permission denied
INFO: tar: ./etc/credstore: Cannot open: Permission denied
INFO: Total bytes written: 6374615040 (6.0GiB, 98MiB/s)
INFO: tar: Exiting with failure status due to previous errors
ERROR: Backup of VM 103 failed - command 'set -o pipefail && lxc-usernsexec -m u:0:100000:65536 -m g:0:100000:65536 -- tar cpf - --totals --one-file-system -p --sparse --numeric-owner --acls --xattrs '--xattrs-include=user.*' '--xattrs-include=security.capability' '--warning=no-file-ignored' '--warning=no-xattr-write' --one-file-system '--warning=no-file-ignored' '--directory=/var/tmp/vzdumptmp1764585_103' ./etc/vzdump/pct.conf ./etc/vzdump/pct.fw '--directory=/var/tmp/vzdumptmp1764585_103' --no-anchored '--exclude=lost+found' --anchored '--exclude=./tmp/?*' '--exclude=./var/tmp/?*' '--exclude=./var/run/?*.pid' . | zstd '--threads=1' >/var/lib/vz/dump/vzdump-lxc-103-2026_01_03-23_57_36.tar.dat' failed: exit code 2
INFO: Failed at 2026-01-04 00:00:37
INFO: Backup job finished with errors
INFO: notified via target `mail-to-root`
TASK ERROR: job errors
INFO: starting new backup job: vzdump 103 --compress zstd --remove 0 --storage local --mode stop --notification-mode notification-system --notes-template '{{guestname}}-pray' --node skylake1
INFO: filesystem type on dumpdir is 'zfs' -using /var/tmp/vzdumptmp1771667_103 for temporary files
INFO: Starting Backup of VM 103 (lxc)
INFO: Backup started at 2026-01-04 00:02:05
INFO: status = running
INFO: backup mode: stop
INFO: ionice priority: 7
INFO: CT Name: forgejo
INFO: including mount point rootfs ('/') in backup
INFO: stopping virtual guest
INFO: creating vzdump archive '/var/lib/vz/dump/vzdump-lxc-103-2026_01_04-00_02_05.tar.zst'
INFO: tar: ./root: Cannot open: Permission denied
INFO: tar: ./etc/credstore.encrypted: Cannot open: Permission denied
INFO: tar: ./etc/credstore: Cannot open: Permission denied
INFO: tar: ./var/cache/private: Cannot open: Permission denied
INFO: tar: ./var/spool/cron/crontabs: Cannot open: Permission denied
INFO: tar: ./var/lib/private: Cannot open: Permission denied
INFO: tar: ./var/lib/docker: Cannot open: Permission denied
INFO: tar: ./var/log/private: Cannot open: Permission denied
INFO: Total bytes written: 6374912000 (6.0GiB, 85MiB/s)
INFO: tar: Exiting with failure status due to previous errors
INFO: restarting vm
INFO: guest is online again after 77 seconds
ERROR: Backup of VM 103 failed - command 'set -o pipefail && lxc-usernsexec -m u:0:100000:65536 -m g:0:100000:65536 -- tar cpf - --totals --one-file-system -p --sparse --numeric-owner --acls --xattrs '--xattrs-include=user.*' '--xattrs-include=security.capability' '--warning=no-file-ignored' '--warning=no-xattr-write' --one-file-system '--warning=no-file-ignored' '--directory=/var/tmp/vzdumptmp1771667_103' ./etc/vzdump/pct.conf ./etc/vzdump/pct.fw '--directory=/mnt/vzsnap0' --no-anchored '--exclude=lost+found' --anchored '--exclude=./tmp/?*' '--exclude=./var/tmp/?*' '--exclude=./var/run/?*.pid' ./ | zstd '--threads=1' >/var/lib/vz/dump/vzdump-lxc-103-2026_01_04-00_02_05.tar.dat' failed: exit code 2
INFO: Failed at 2026-01-04 00:03:22
INFO: Backup job finished with errors
INFO: notified via target `mail-to-root`
TASK ERROR: job errorsok this officially got much harder - 95% sure i installed trixie's debian 13 version on bookworm in the couple weeks before the trixie release https://github.com/community-scripts/ProxmoxVE/blob/main/install/forgejo-install.sh#L23-L24 this doesnt check the release of the current CT it pulls the release from latest from the codeberg repo - so theres a large window without overlap #!/bin/bash
set -euo pipefail
# Forgejo paths to backup
PATHS=(
/var/lib/forgejo/
/etc/forgejo/
/etc/systemd/system/forgejo.service
/opt/forgejo/
/home/git/
/usr/local/bin/forgejo
)
BACKUP_FILE="forgejo_backup.tar.gz"
echo "Creating backup: $BACKUP_FILE"
tar -czf "$BACKUP_FILE" --absolute-names "${PATHS[@]}"
echo "Done. Size: $(du -h "$BACKUP_FILE" | cut -f1)"echo '#!/bin/bash
set -euo pipefail
# Forgejo paths to backup
PATHS=(
/var/lib/forgejo/
/etc/forgejo/
/etc/systemd/system/forgejo.service
/opt/forgejo/
/home/git/
/usr/local/bin/forgejo
)
BACKUP_FILE="forgejo_backup.tar.gz"
echo "Creating backup: $BACKUP_FILE"
tar -czf "$BACKUP_FILE" --absolute-names "${PATHS[@]}"
echo "Done. Size: $(du -h "$BACKUP_FILE" | cut -f1)"' | tee forgejo_backup.sh
chmod +x forgejo_backup.sh
./forgejo_backup.sh tar -tzf forgejo_backup.tar.gz --absolute-names # to extract it back
tar -tzf forgejo_backup.tar.gz | less # to just view the contentshavent tested it yet on a fresh install, but it should work, ill report back when i do |
|
ok ignore previous i still feel like most of the issues stem from https://github.com/community-scripts/ProxmoxVE/blob/main/install/forgejo-install.sh#L23-L24 i tried to install forgejo runners following: https://forgejo.org/docs/latest/admin/actions/runner-installation/ i think ive come up with a few scripts to diagnose and treat whatever i got myself into, YMMV FROM INSIDE CONTAINER - Audit #!/bin/bash
set -euo pipefail
echo "=== Container Audit ==="
dpkg --audit || echo "No broken packages"
echo ""
echo "Failed services:"
systemctl --failed --no-legend || echo "None"
echo ""
echo "Services:"
systemctl is-active docker systemd-logind ssh || true
echo ""
echo "Files owned by nobody:"
find / -user nobody -not -path '/proc/*' -not -path '/sys/*' -not -path '/dev/*' -ls 2>/dev/null | head -10 || echo "None"
echo ""
echo "Directory permissions:"
ls -ld /root /var/lib/systemd /var/lib/docker /var/cache/man /var/log/journal 2>/dev/null || true
echo ""
echo "Permission errors in logs:"
journalctl -p err -b | grep -i "permission\|operation not permitted" | head -5 || echo "None"
echo ""
echo "APT test:"
apt-get update -qq 2>&1 | grep -i "error\|fail" || echo "OK"
echo ""
mandb -q 2>&1 | grep -i "permission" | head -3 || echo "mandb OK"FROM PROXMOX HOST - Audit bash -c '
CT_ID=${1:-103}
M=$(zfs get -H -o value mountpoint rpool/data/subvol-${CT_ID}-disk-0 2>/dev/null || exit 1)
echo "=== Host Audit CT ${CT_ID} ==="
echo "Mapped nobody (165534):"
find $M -uid 165534 -not -path "*/proc/*" -not -path "*/sys/*" -not -path "*/dev/*" 2>/dev/null | wc -l
echo "Unmapped nobody (65534):"
find $M -uid 65534 -not -path "*/proc/*" -not -path "*/sys/*" -not -path "*/dev/*" 2>/dev/null | wc -l
echo ""
echo "Critical dirs ownership:"
for d in root var/lib/systemd var/lib/docker var/cache/man var/log/journal; do
[ -e $M/$d ] && echo "$d: $(stat -c "%u:%g" $M/$d 2>/dev/null || echo "?")"
done
echo ""
pct config $CT_ID | grep unprivileged
'FROM PROXMOX HOST - Fix bash -c '
CT_ID=${1:-103}
M=$(zfs get -H -o value mountpoint rpool/data/subvol-${CT_ID}-disk-0 2>/dev/null || exit 1)
echo "Fixing CT ${CT_ID}..."
pct stop $CT_ID
chmod 700 $M/root && chown 100000:100000 $M/root
chown -R 100000:100000 $M/var/lib/systemd $M/var/lib/docker $M/var/cache/man $M/var/log/journal $M/etc/credstore* $M/var/cache/private $M/var/lib/private $M/var/log/private 2>/dev/null || true
chmod 600 $M/root/.bash_profile $M/root/.bashrc 2>/dev/null || true
chown 100000:100000 $M/root/.bash_profile $M/root/.bashrc 2>/dev/null || true
find $M/var/tmp -type d -name "systemd-private-*" -exec chown -R 100000:100000 {} \; 2>/dev/null || true
find $M -uid 165534 -not -path "*/proc/*" -not -path "*/sys/*" -not -path "*/dev/*" -exec chown 100000:100000 {} \; 2>/dev/null || true
find $M -uid 65534 -not -path "*/proc/*" -not -path "*/sys/*" -not -path "*/dev/*" -exec chown 100000:100000 {} \; 2>/dev/null || true
pct start $CT_ID
echo "Done"
' |
|
The only lxc container that didn't work after updating was TasmoAdmin, and the OS itself just worked fine. I just needed to uninstall php8.2 and install php8.4 (and the dependencies): |
|
Upgraded NGINX Proxy Manager (default install with simple setup) |
|
NGINX Proxy Manager got Fixed by Then do regular upgrade, now confirmed this works |
|
Am i supposed to run that before the Trixie upgrade? Still not working for me... |
|
@tokr1 no after the upgrade. Without adding any error, noone can help you. Did it fail during the upgrade or does nginxproxymanager just not work afterwards? |
|
Sorry about that, it was late last nite
|
|
Updating NginxProxyManager using the I think the sources for NodeJS and Openresty should be checked within the upgrade script. I am not sure what the correct values are and how to fix this |
|
we can't fix this, we need to wait till it's fixed in the nodesource and openresty repos, this has been reported already so many times in this thread and we can't do anything about it. Nodesource has been fixed upstream some days ago and we are working on automatic a solution for all users. |
|
It worked for Nginx Proxy Manager LXC inside Proxmox VE 8.4.16. I needed it to upgrade Nginx Proxy Manager itself. I had trouble with these openresty errors, but Google Gemini helped me to worked it out and now it's all fine. Thank you all |
|
yes same here. But i didt resolv based on gemini unfortunately |
How do you solved the NPM update? I have openresty the issue to. |
|
@kintaro1981 Try after this merges: |
|
Nginx Proxy Manager From v2.13.7 to v2.14.0 Fixed by Then update again |
|
Upgraded the following LXCs from Debian 12 to Debian 13: CTID Hostname OS100 paperless-ngx Debian GNU/Linux 12 (bookworm) Everything flawless except paperless-ngx. After upgrading I receive "500 Internal Server error". Skipping DB Update does not change this, wating 10+ minutes or rebooting with no success so far. Rolled back via Snapshot for now. |
|
did you manage to fix the paperless-problem at some point? |
|
Is this still the recommended way to update a LXC Container? By the way: One of my LXCs is still on Debian 11. Can it be upgraded the same way? |
|
@io2345 I guess so. I would be cautious with that, but i guess with proper backup it's worth a shot, possibly if the app allows data export, it may be better to export data and recreate the container. EDIT: But make sure to do this step by step, e. G. first to bookworm then to trixie. |
|
Thank you, CrazyWolf13. I will dare to update the next days. If it goes wrong, I can still recreate the conainters from the backup, right? As for the Debian 11 container: Is there a script for LXC update bullseye -> bookworm as well? |
|
You can try this: apt-get update
apt-get install screen -y
apt-get upgrade -y
sed -i 's/bullseye/bookworm/g' /etc/apt/sources.list
apt-get update
screen apt-get dist-upgrade
apt-get autoremove
apt-get autoclean
apt-get clean
apt-get update
reboot |
|
Could update the Jdownloader2-Container first to Debian 12 and then to 13. Up and running fine. ... Is there anything I can do to get that fixed? |
|
we dont have an jdownloader container? your gpg keys are broken for influx, you need to download the current gpg |
|
It's probably best to look at influxdb wiki on how to install on debian and remove the old entries. |
|
In fact that was the easiest part and can be fixed in seconds. A good guide in german can be found here: https://darkwolfcave.de/influxdata-gpg-key-problem-loesung/ |
|
Successfully upgraded Trilium with no issues. |
|
Hello I mean I've created that lxc some time ago, now when I want update with update command its say script is for 13 and you are on 12 it could not work. Status: Downloaded newer image for ghcr.io/home-assistant/home-assistant:stable
ghcr.io/home-assistant/home-assistant:stable
⠇ Updating All Containerserror: externally-managed-environment
× This environment is externally managed
╰─> To install Python packages system-wide, try apt install
python3-xyz, where xyz is the package you are trying to
install.
If you wish to install a non-Debian-packaged Python package,
create a virtual environment using python3 -m venv path/to/venv.
Then use path/to/venv/bin/python and path/to/venv/bin/pip. Make
sure you have python3-full installed.
If you wish to install a non-Debian packaged Python application,
it may be easiest to use pipx install xyz, which will manage a
virtual environment for you. Make sure you have pipx installed.
See /usr/share/doc/python3.13/README.venv for more information.
note: If you believe this is a mistake, please contact your Python installation or OS distribution provider. You can override this, at the risk of breaking your Python installation or OS, by passing --break-system-packages.
hint: See PEP 668 for the detailed specification.
✖️ in line 46: exit code 1 (General error / Operation not permitted): while executing command pip install -U runlike
--- Last 20 lines of log ---
[2026-07-29 13:23:24] Home Assistant Update Options
[2026-07-29 13:23:26] [INFO] Updating All Containers
[2026-07-29 13:24:12] [ERROR] in line 46: exit code 1 (General error / Operation not permitted): while executing command pip install -U runlike
-----------------------------------Anything I am doing wrong? If I am in wrong topic please point correct one. |
|
Worked well, did not have any issues upgrading deb-12 for Pi-hole, and Adguard, going to slowly run through some of my older LXCs. |
|
Hello, I just migrated Nginx Proxy Manager to Trixie without problems. Thank you to the OP. BR. |
|
A lot of scripts have moved on to Debian 13 from 12 and warn when you update to update to 13 first. Is there an official guide or script to do that as painless as possible? Hacking around in the console isn't really user friendly and abandons everyone who has used scripts with Debian 12. Besides, this guide doesn't mention how much free disk space is needed for the upgrade to complete sucessfully. A lot of small LXCs are configured very limited by default. |
|
It's not really a process that can be easily automated, as things can break and there are a lot of different setups, configs, third-party repos, customizations, and dependencies. There simply isn't a safe, universal way to automate a major Debian release upgrade, which is also why we haven't written our own script for it. Even Debian's official upgrade process requires some checks and occasional decisions depending on the system. But you've found the correct thread, which features a guide at the top. I recommend reading it carefully, taking proper backups, and just starting with an LXC. It's really not much advanced work in the console. There may be some occasional prompts, but you can easily Google them or ask AI. Most of the time, it's just accepting the defaults. If you're not familiar with the console yet, it's also a bit of a learning experience. By now, many things have matured and the updates should go through quite smoothly. At the end, just run |
|
I see. I upgraded one LXC and was surprised by some questions that were asked, mainly it was about if existing configs should be kept or replaced. This thread is getting a bit confusing. Is there at least a maintained list of which LXC can safely be upgraded (like in the first few posts but consolidated)? A few general points of advise (like the most common checks as I encountered them about configs or the most common errors) would also be very helpful for people not deeply familiar with Linux Distro upgrades. Maybe creating a help page that lists all this on the main website instead of having it burried in this discussion is what I was looking for. |
|
generally this was a problem almost a year ago, when debian 13 was new, now most of the things are pretty much standard, e.g. you can also simply use any guide on how to update debian 12 to debian 13. As far as I can tell, you should be pretty much safe to upgrade any lxc. except from those which have default os: debian_12, I shortly checked our DB, and those are still on debian12, to save you the time of checking each LXC. allstarlink-vm edit: thanks for bringing this topic up, I just upgraded a bunch of scripts and added a comment about the current status, here: #7332 |
and others
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Looking for Debian 13 Upgrade Testers
We are currently looking for testers for Debian 13 (Trixie) in our LXC scripts.
At this stage, support will most likely only work on Proxmox VE 9 (currently 9.0). Proxmox VE 8.x is not targeted for Debian 13 support.
Caution
The following post is intended as Beta-test, proceed with Caution and ensure full Backups are created.
The ideal commands we recommand to update a Debian 12 (Bookworm) LXC to Debian 13 Trixie:
What it does
This will install the latest updates, install screen (kinda like a virtual terminal) this makes sure the update continues to run even if the ssh session would get interrupted, the user can just run
screen -rto re-attach to the update process.After that it will rewrite the sources to Trixie and upgrade everything.
Then existin source files will be rewritten to the new deb822 format.
Caution
Proceed with Caution, this may break your LXC, so be sure to create proper Backups beforehand.
Important
Check out this thread for more info on what LXC have issues upgrading and keep up to date on their status:
#7332
apt update apt install screen -y apt upgrade -y sed -i 's/bookworm/trixie/g' /etc/apt/sources.list apt update screen apt dist-upgrade apt autoremove apt autoclean apt modernize-sources apt update rebootTip
After the upgrade the MOTD (Message displayed on SSH login, will still show Debian 12, check out this guide on how to regenerate it.
#7227
Note
For new installations of a LXC, check this thread:
#7485
Warning
Please only report the apps that don't work. as otherwise this discussion get's a bit flooded.
Thanks!
We would appreciate your feedback
Simply let us know which scripts are working and which are not.
We will continuously clean up and update this post based on your reports.
Thank you for helping us move Debian 13 support forward 🙌
CrazyWolf13 (Community-Scripts-Team)
All reactions