I can understand the desire for it in Alma, since it's primarily a replacement for Scientific-Linux, and will be on a lot of cloud services, but anytime you add a requirement for something to basically function, you increase the likelihood that it won't.
this post was submitted on 14 Oct 2024
24 points (100.0% liked)
Linux
5187 readers
71 users here now
A community for everything relating to the linux operating system
Also check out [email protected]
Original icon base courtesy of [email protected] and The GIMP
founded 1 year ago
MODERATORS
What requirement would that be?
I have not used Alma in daily usage.
I think as a "just works" Workstation it is great, based on the giants, and bootc makes it even more stable.
By using EPEL, KDE, or even CentOS Stream and Hyperscale packages (which Meta does in production but I can imagine not everyone wants to do), you get more instability. This could be mitigated with the atomic structure.
Also, instead of full Hyperscale, the COPR kwizart/kernel-longterm could be used, which is the more current, official LTS kernel.
No thanks, adding unnecessary complexity decreases reliability and efficiency. Might make it easier to migrate things to AWS, also a negative.
Where is the complexity?
A compose file can literally be
FROM quay.io/almalinuxorg/almalinux-bootc:9.4
# Add files from same directory
ADD somefile /etc/somefile
# Add EPEL repository
RUN dnf install -y epel-release
# Install KDE Desktop environment
RUN dnf groupinstall -y "KDE Plasma Workspaces"
# Install flatpak, podman, distrobox, and fish
RUN dnf install -y flatpak podman distrobox fish
RUN systemctl enable sddm
Done, build an ISO, push the images to a registry and you have made your own "distro". There are at least 3 implementations, on Github, Gitlab and Codeberg, so you can use their individual runners
How can I get set up going from the Containerfile to an ISO?