Or asked the other way around: How long do you keep your servers running without installing any software updates?
update means something like
sudo dnf update
or something …
apt-get upgrade
apt-get update
Those apt commands are in a less-good order. It’s usually better to update apt, then upgrade the system.
I upgrade as soon as reasonably possible after the notification appears, if the system isn’t on auto-upgrade.
I do
sudo apt update && sudo apt upgradeIs there any reason to not combine the commands since the output always prompts prior to changes anyway?
I think their point was to make sure they are done in order, i.e. update before upgrade, not the other way around as in OPs example.
Whenever I ssh into it.
Every night at ~ 12-1am
unattended updates / transactional-update are awesome.
Stuff has been running for years, and it’s still up to date.
This guy scares me
Unattended-upgrade does security-only patching once every 4 hours (in rough sync with my local mirror)
Full upgrades are done weekly, accompanied by a reboot
I find that the split between security patching and feature/bug patching maintains a healthy balance knowing when something is likely to break but never being behind on the latest cve.
Well, one of the reasons I’m using debian on my server is so I can kinda forget about it…
I’ll update maybe once a month, or every couple months. I don’t always restart though, so my kernel is probably a bit behind :'D
When I remember. About once a month.
Monthly unless I learn about a vulnerability that would require it sooner.
Every day or at least once a week. Should automate it.
Should; Could; How high of a priority is this update automation for you? This is also how I run my server. Configuration possibilities are infinite.
On Alpine Linux I update my two Pi servers at 2 in the morning daily. It’s simpler compared to Debian which needs unattended-updates. Just add
apk update && apk upgradeto a cron job and you’re good to go.I only have three docker services which is simple enough to update manually.
I like to keep things as simple as possible for my already chaotic brain.
Be careful with unattended upgrades, even on alpine. A recent breaking change in python3 broke my alpine 23 ansible instance. Thankfully I have backups, but if you’re going to automate the upgrade, you should automate tests as well.
My web facing server has just enough packages installed to (kinda securely) host a Caddy and Kiwix docker container to work with my domain name and make a comfortable work environment through SSH. My Pi for my HomeAssistant docker container has less because it’s locked down to just my local network.
I also wrote my own install scripts so reinstalling everything and getting it back to a running state would take about 15 minutes for each device.
And I also wrote my own backup/restore scripts that evolved over 3/4 of a year. I use them often so I have confidence in those scripts.
I personally don’t really care too much. I have multiple ways of dealing with issues for something that’s a hobby to me. Which is why I stick to simplicity.
I’m sure this is a thing for people to worry about when dealing with more complex setups. I just wanna vibe out in my tiny corner of the internet.




