Another week. Another distro.
Fine. I’ll add it to my collection.
this post was submitted on 15 Aug 2024
31 points (100.0% liked)
Linux
8028 readers
11 users here now
Welcome to c/linux!
Welcome to our thriving Linux community! Whether you're a seasoned Linux enthusiast or just starting your journey, we're excited to have you here. Explore, learn, and collaborate with like-minded individuals who share a passion for open-source software and the endless possibilities it offers. Together, let's dive into the world of Linux and embrace the power of freedom, customization, and innovation. Enjoy your stay and feel free to join the vibrant discussions that await you!
Rules:
-
Stay on topic: Posts and discussions should be related to Linux, open source software, and related technologies.
-
Be respectful: Treat fellow community members with respect and courtesy.
-
Quality over quantity: Share informative and thought-provoking content.
-
No spam or self-promotion: Avoid excessive self-promotion or spamming.
-
No NSFW adult content
-
Follow general lemmy guidelines.
founded 1 year ago
MODERATORS
Could be an interesting base for DistroBox.
The reason I use Fedora and not EL like Almalinux are the newer kernels and graphics drivers.
They are often crucial for playing relatively new games. When I used Debian before, I was blocked from playing several games that used a newer Version of DLSS or FSR before because my outdated drivers wouldn't work for them.
So I don't understand how Oreon was "designed with gaming in mind" by shipping old software and lts kernels + drivers.
Just because Steam, Lutris and Bottles are preinstalled (or available as Flatpaks)?
Edit: I see it comes with RPM Fusion repos out of the box. Good decision.
docker preinstalled
This is actually perfect. My main issue with EL distros is that they tend to push podman, which is not a 1-to-1 replacement for docker. This may end up being my default for non-immutable OS installs.
I'm trying to learn Podman because Fedora atomic is the way I want to go right now, but getting firewalld to cooperate is enraging. Are you hitting problems other than that?
Oddly enough: SELinux and file ownership for bind mounts were pretty hellish for me, even with :z. Granted, that's definitely on me (skill issue) for having misconfigured SELinux policies, but docker got out of my way.
Other than that, my gripes about podman have to do with inter-container DNS communication and having to creating systemd services to manage simple container stacks. That last one is a major thorn in my side because the podman CLI used to have a simple command to generate the systemd file for you, but they're getting rid of it.
I run containers locally for basic dev work and, on occasion, deploy simple self-hosted services. In both of those cases, I find Podman to be an unnecessary hindrance where Docker isn't.
It's foolish to remove a tool to generate systemd files, running containerized services is one of the main uses of tools like these. That is a big disappointment.
Oddly enough: SELinux and file ownership for bind mounts were pretty hellish for me, even with :z. Granted, that's definitely on me (skill issue) for having misconfigured SELinux policies, but docker got out of my way.
Yes, SELinux can be painful to troubleshoot. I assume the bind mount path may not have been labeled containerfile_t
That last one is a major thorn in my side because the podman CLI used to have a simple command to generate the systemd file for you, but they're getting rid of it.
That command was indeed helpful. They replaced it with quadlets. Systemd quadlets were not that hard to configure as I initially thought though. I migrated my 10 services with their dependent containers, volumes and networks within a few hours or so. The manpage is well written and shows examples https://docs.podman.io/en/v4.6.1/markdown/podman-systemd.unit.5.html
Of course there's nothing wrong with using docker if it fits better