Comment by tekacs 7 days ago
Fun seeing HN restart to switch to the Christmas theme, in three steps:
https://share.cleanshot.com/vJZv6k03 (restarting the server)
https://share.cleanshot.com/qFyM347P (online but temporarily readonly)
https://share.cleanshot.com/kW8kY7mp (back online!)
Dear Santa, for Christmas can we get a prefers-color-scheme: dark mode for HN, thank you and Merry Christmas
Color me confused, but what do containers add to FreeBSD beyond jails? Jails have their own IP addresses and root filesystem, plus they use the host OS's version of libc and OpenSSL/LibreSSL and all the other core utils.
Is it the convenience utilities for building and running container images?
But alas, FreeBSD does support OCI container images! It supports Podman and has an OCI-compliant runtime:
https://freebsdfoundation.org/blog/oci-containers-on-freebsd...
However, I still can't pinpoint what the value proposition is compared to using jails. Is there anybody around here able and willing to shed some light? I know I didn't use Cunningham's Law to start the conversation like a clever netizen but maybe, just this once, a good faith response to a good faith question is possible.
Tbh like 99% of web apps aren’t critical - most of them are for buying something or providing infrastructure to make it easier to buy something anyway. It’s fine if your online shop is down for a few minutes (of course the business won’t see it like that but it’s true)
B&H is doing fine financially and brings their webstore down for each and every Sabbath, even if that happens to be a Black Friday.
A sales site being down might lose you a sale. But the simplicity might save you so muh more than that loses you. And often the complexion of high availability infrastructure results in more downtime than it prevents.
For stuff like HN, I like the peek behind the scenes it provides. It's all just software written by some humans and way too often people take themselves and their shitty software way too serious.
I feel like this obsession with zero downtime has gotten a bit silly. Sure, for some things it's damn near required (though I imagine that's fewer things than most people think), but it 100% does not matter even a little bit if HN is unavailable for 10 seconds or so.
Everyone went right for “downtime” - no, that’s not an issue. I would have expected a configuration change, which wouldn’t require a restart but might indeed result in downtime.
Or even a configuration change that some control system notices and does restart the service.
It’s the manual, hands-on connotation (maybe only in my mind) of telling someone a restart is involved. Automate this stuff - don’t want the code in the server all year? Fine, have a process rebuild and relaunch on a schedule that makes sense. Might have downtime, but definitely have less hands-on.
You must have grabbed that first one awfully quickly!