You're not supposed to run apt upgrade in Proxmox at all, it may even break your system. Use dist-upgrade.
https://pve.proxmox.com/pve-docs/chapter-sysadmin.html#system_software_updates
dist-upgrade and full-upgrade are essentially the same command but yeah, I won't be using apt upgrade again in the future! Like I said in my post, the joys of being self taught is that you learn by my making mistakes and that's part of the "fun" 🤣
Nah, the fun is learning form others mistakes. Thanks for a fun read :}
Not essentially, exactly. One is a deprecated alias for the other.
Which one is which?
I thought full-upgrade replaced dist-upgrade that could make you think you're upgrading you distro to the next version
But now I'm not sure anymore.
Correct. Full-upgrade is the new term. It's an alias, though, so using either will accomplish the same thing.
dist-upgrade was used with apt-get
full-upgrade is used for apt
Just don’t use any command in proxmox. Proxmox is designed GUI first. It got an update button in the GUI. Only major releases could need tinkering in the terminal. But even changing repos is now possible in the GUI.
Gets annoying soon if you have more than one host. Easily automated with Ansible
gotta love that GUI, that bombards you with reminders to subscribe to their paid tier repository constantly and won't let you update...
also, provides no methodology to control when it wants to overwrite a config or when a externally added signable dkms exists and creates a prompt during dkms building.
the gui is nice, but it's far from perfect...
I'm curious, how might apt upgrade break something in Proxmox?
I don't know, I've seen it several times mentioned in the Proxmox forum. I think it's more of a theoretical scenario but it's strongly advised against.
Hmm. Welp. Let’s try. See what happens.
I've seen that the patches are only available in the debian-security repository. It's important to review your repo list in /etc/apt/sources.list.d.
Proxmox does not use the standard debian kernel.
Yes, I referred to the Debian part only.
I mean, you could just use the proxmox UI for updates. Single point for all servers, just click in and hit update. It explicitly runs dist-upgrade already.
Is this just a Proxmox thing? I'm running Debian on my server, and as far as I know, the kernel has always upgraded properly when there's a new one available.
Ooof, scared me there for a second. Good thing I am using Dist-Upgrade in my ansible scripts.
The nice thing about zypper is the various patch options and reporting. Gives you a good picture of what CVEs, rating, and if installed, needed, not needed etc. Does Apt have something similar?
I honestly don't know what your talking about. proxmox updated the pve kernels immediately after this CVE was published....
additionally, this CVE only applies to older (pre-6.17 kernels). unless you are on proxmox 8 or earlier, you are already running a "patched" kernel as the pathway necessary for this was changed and in kernel 7.x and above this CVE doesnt work...
from my own experience, apt dist-upgrade removes old kernels, apt upgrade still installed the new kernel, grub updated and booted into the new kernel.
all dist-upgrade did (for me) was delete the old kernels. which is something I would prefer not to do because it removes any ability to rollback should I absolutely need to.
Which distro? Debian for example always keeps two kernels: the curent one and the one in use before that, which is what I prefer, never had to rely on more than one backup kernel.
Debian. like the Debian.
currently running Trixie on my daily and bookworm on a couple servers which will be upgraded to Trixie soon.
@GreenKnight23 @oong3Eepa1ae1tahJozoosuu I've never seen that behavior in Debian. Is that some different type of configuration?
native config. nothing special.
@GreenKnight23 I don't see that behavior. Rebooting into a new kernel and then running dist-upgrade, it always _always_ keeps one older kernel around. Bookworm and trixie.
You only need the reboot if a package update masks the retirement.
The system is not lying to you, it holds some critical updates back to be installed separately and manually.
The output shows you which packages have been held back. Just do apt-get install linux-image-amd64 for example, reboot and apt autoremove to remove the old kernel.
A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.
Rules:
Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
No spam posting.
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
No trolling.
No low-effort posts. This is subjective and will largely be determined by the community member reports.
Resources:
Any issues on the community? Report it using the report flag.
Questions? DM the mods!