this post was submitted on 02 May 2026
97 points (94.5% liked)

Selfhosted

58906 readers
767 users here now

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:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. 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.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

  7. 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!

founded 2 years ago
MODERATORS
 

cross-posted from: https://lemmy.ml/post/46701277

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
[–] tofu@lemmy.nocturnal.garden 51 points 21 hours ago (2 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

[–] TheIPW@lemmy.ml 22 points 20 hours ago (2 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" 🤣

[–] MalReynolds@slrpnk.net 13 points 15 hours ago

Nah, the fun is learning form others mistakes. Thanks for a fun read :}

[–] frongt@lemmy.zip 7 points 20 hours ago (1 children)

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

[–] Infernal_pizza@lemmy.dbzer0.com 4 points 14 hours ago (2 children)
[–] whyNotSquirrel@sh.itjust.works 5 points 11 hours ago (1 children)

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.

[–] K3can@lemmy.radio 3 points 9 hours ago

Correct. Full-upgrade is the new term. It's an alias, though, so using either will accomplish the same thing.

[–] Staff@piefed.world 1 points 8 hours ago* (last edited 8 hours ago)

dist-upgrade was used with apt-get

full-upgrade is used for apt

[–] LeTak@feddit.org 1 points 17 hours ago (1 children)

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.

[–] tofu@lemmy.nocturnal.garden 7 points 17 hours ago

Gets annoying soon if you have more than one host. Easily automated with Ansible