98
Turns out I have been updating wrong all this time! 🤦🏼 (the.unknown-universe.co.uk)
submitted 6 months ago by to c/selfhosted@lemmy.world
24 comments fedilink hide all child comments
 

I’ve been running my home lab since 2021 and honestly thought my update routine was solid: apt update && apt upgrade, reboot, job done.

Turns out I was wrong. I was checking CVE‑2026‑31431 (Copy Fail) this morning and realised that despite my “successful” updates, I was still running a vulnerable kernel from March.

I’ve had to rethink how I handle host updates. If you’re relying on a standard upgrade and a reboot to keep Proxmox or Debian hosts safe, you might want to check if yours is lying to you as well.

you are viewing a single comment's thread
view the rest of the comments
[–] 58 points 6 months ago (8 children)

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

  • permalink
  • fedilink
  • source
  • hideshow 8 child comments
    •
  • [–] 28 points 6 months ago (5 children)

    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" 🤣

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 5 child comments
    •
  • [–] 6 points 6 months ago (3 children)

    Not essentially, exactly. One is a deprecated alias for the other.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 3 child comments
    •
  • [–] 5 points 6 months ago (2 children)

    Which one is which?

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •