How Red Hat just quietly, radically transformed enterprise server Linux
Posted by CrankyBear@reddit | linuxadmin | View on Reddit | 36 comments
Posted by CrankyBear@reddit | linuxadmin | View on Reddit | 36 comments
Practical_Form_1705@reddit
I imagine that image mode will apply more to VMs, than bare metal installation, so it will be only an option.
gordonmessmer@reddit
I'm happy to be corrected, but I am not aware of RHEL discarding traditional packaging. Image Mode is an option, but "traditional packaging" is still a supported configuration.
CrankyBear@reddit (OP)
You're right. It is.
mmcgrath@reddit
Yeah... Red Hat is headed towards.... Choice.
BanazirGalbasi@reddit
Fedora Silverblue has been around for 6.5 years (released Oct 2018) and yet standard Fedora is still going. As far as I know, Silverblue is the less popular of the two, too.
Just because the immutable option exists doesn't mean that it's going to become the default.
Resource_account@reddit
If you group all the main “spins” (Gnome, KDE, Sway, etc) and include Silverblue, I don’t think Silverblue would even be in third place in terms of usage. This is coming from someone who daily drives it. Not sure if Fedora tracks downloads per spin/version but would love to see some stats.
ABotelho23@reddit
In what sense? dnf is still used to build the images.
Nnyan@reddit
Please don’t link steven vaughan-nichols trash articles.
linux_traveler@reddit
It’s good news to know that AI is not the only way to write trash articles 😃
Nnyan@reddit
Damn, take my upvote.
Codetard1@reddit
Yeah, this guy just keeps spamming this zdshit website
im-tv@reddit
Hmm, I thought IBM acquired RedHat some time ago.
__2M1@reddit
They did
frank-sarno@reddit
https://www.redhat.com/en/blog/image-mode-for-red-hat-enterprise-linux-generally-available
This is the Image Mode that was previewed earlier.
From the above:
"If you love using package mode, fear not. There is no intent to do away with it, or force users to change modes. Each mode has different advantages, and we encourage everyone to use what's best for their workloads and operational preferences."
So not going away but now generally available. I have used SilverBlue previously and found it interesting but wasn't quite ready when I played with it last year.
doubled112@reddit
I really like the immutable OS concept, but it doesn’t solve any real problems I have.
I’m not at a scale I need a bunch of identical machines, and the ones I have are mostly still pets not cattle.
Maybe some day.
iavael@reddit
On desktops with flatpaks for gui apps and nixpkgs for cli tools, it works wonderful.
For server application with deployment via podman or kubernetes, it works fine, too.
spicybeef-@reddit
I use nixos and am curious why flatpaks for gui apps instead of nixpkgs? Is it so you can get more frequent updates while using the stable channel for cli tools?
iavael@reddit
Faster update process (only changed files are downloaded instead of redownloading whole new package again in archive).
Earlier push of new releases in case of flathub (it promotes upstream involvement in support of flatpak).
Better isolation. Especially regarding home directory: programs keep their crap in their own subdirectories instead of shitting all over ~ (very useful for steam and its games)
circularjourney@reddit
I am suspicious most people are in the same boat.
I like the idea of a bootable container, and will likely switch to this someday in the distant future, but I just don't see the rush. This solves a problem I almost never experience with my host OS (desktop or server), but I will concede is always a possibility.
I keep my host OS super simple and container everything I possibly can (desktop & server). Doing this keeps the update cycle pretty much error free, for the containerized application and my host OS.
clavicle@reddit
How do you ensure you're keeping your container images up-to-date?
frank-sarno@reddit
Yes, it's definitely in its early stages. I can see its utility, however. The ability to do updates without worry was one potential feature as is the ability to rollout a bunch of idential machines. You can do this with non-immutable distros certainly but I can see how the new approach can make it more robust.
ancientweasel@reddit
It wasn't quiet.
bityard@reddit
Meanwhile, the tech company I work for finally upgraded off of RHEL/CentOS 7 this year...
(Well, mostly...)
kennedye2112@reddit
If it makes you feel any better, we seconded our last RHEL 6 systems in February. Only about 1700 RHEL 7s to go!
squeeby@reddit
That article is incredibly opinionated, and doesn’t even mention that immutability is optional.
It reads like RedHat is enforcing atomic updates, and that package based software is being completely discarded.
This is why we need to fact check absolutely everything these days, because of the narrow minded “I learned about this 6 minute ago so now I’m going to write about it” authors.
nut-sack@reddit
Thanks, I was worried this is the intended method of using RHEL10.
surveypoodle@reddit
Is this like Fedora CoreOS or something else?
Intergalactic_Ass@reddit
Utterly dogshit article. Trash.
sha1dy@reddit
is this similar to the NixOs and the like?
iavael@reddit
No, only in regard of immutability. But it's implemented in very different ways.
terAREya@reddit
2025 is the year of the Linux desktop though
Vogtinator@reddit
SLE Micro has been out for several years by now and SLES Transactional Server is even older.
No_Rhubarb_7222@reddit
I mean we can, by that logic, say that RHEL Atomic and CoreOS have been out for many years as well.
I think the noteworthy thing is that this is now a supported build and deployment method for the OS and that large Red Hat customers have already started using it this way.
Vogtinator@reddit
SLE Micro has been out for several years by now and SLES Transactional Server is even older.
gmuslera@reddit
So, like snap but with docker/podman containers for updated apps? Yes, it is a bit more complex than that, and the devil is in the details, but isn't it a similar strategy?
martian73@reddit
To be clear, immutable RHEL 10 very much uses RPM packages to build the immutable image