Update LXCs running Debian 11 to Debian 12 #1498
Replies: 7 comments 24 replies
-
Is this something we need to manually do for all containers or will the LXC updater script do it? |
Beta Was this translation helpful? Give feedback.
-
In case anyone is running into an issue with yarn install, the problem is the node.js version. You can easily use Node Version Manager --> Install nvm Then use |
Beta Was this translation helpful? Give feedback.
-
I would change the 5 lines to just one with sed -i 's/bullseye/bookworm/g' /etc/apt/sources.list Thats the command that Proxmox is using in their wiki as well for just upgrading the bullseye stuff to bookworm in the sources.list. |
Beta Was this translation helpful? Give feedback.
-
I got this error in several LXC Containers when I try to upgrade: . does anyone have an idea what this can be? |
Beta Was this translation helpful? Give feedback.
-
I get the following when trying to update Adguard to Debian 12 alpine-adguard-sec login: root alpine-adguard-sec:~# cat </etc/apt/sources.list
|
Beta Was this translation helpful? Give feedback.
-
Beta Was this translation helpful? Give feedback.
-
I've been trying to update my Nginx Proxy Manager LXC on Debian 11 to 12 and keep running into problems. I've been able to update to 2.10.4 on Debian 11 no problem. I then execute the instructions in the OP to upgrade to Debian 12. That seems to work okay, but when I visit the NPM homepage and try to login I get "Bad Gateway". Next, I tried re-running the upgrade script and it fails with this error:
I can restore a backup and thankfully that works for now. |
Beta Was this translation helpful? Give feedback.
-
Updating the LXC to Debian 12 manually could potentially cause a loss of functionality.
Here's the approach I took to upgrade mine, but remember to have backups as a precautionary measure.
Copy & Paste in the LXC console
Beta Was this translation helpful? Give feedback.
All reactions