His distros is just arch with some packages and dotfiles on top. Why does he think anyone would base their distro off his?
Voytrekk
- 0 Posts
- 12 Comments
You are correct that they restart a container that has stopped because of a bad exit. I meant a container that has completely disappeared due to running out of storage on the system. Given, that is a failure of configuration to begin with.
Docker compose definitely works for most people, so I would feel pressured to swap.
There is one instance where Quadlets would have fixed an issue we ran into at work. We had a Kafka instance whose container died and went away because we ran out of space on the server. Compose doesn’t recreate containers on failure, so I was called in to fix the issue. Quadlets treats containers as disposable, so it would have recreated it as soon as it went away. The root of the issue was a bad logging config that we fixed on the next business day.
The security of Rocky is solid and RL 10 is supported for quite a long time. I’m also used to RHEL based systems at work, as we target Red Hat.
That being said, I wouldn’t recommend it for most people. SELinux can be annoying to deal with and can cause issues where it isn’t obvious that SELinux is the cause.
If I were to chose again, I would probably just pick Debian as most of my workloads are just running in containers or VMs. The only services running on the host are NFS and Samba.
I migrated from docker containers on Unraid to using quadlets on RockyLinux. The Podlet utility helped a bit with taking an existing docker container and converting it to a quadlet. Also did thorough testing in a VM before swapping my server.
It does have a larger file size compared to compose, sure. The big advantage of quadlets is that systemd will handle things in the event of a failure. It makes it a great option for production environments where you will not need to update your config files as much. It also allows you to have more control over when each application starts, if they rely on a specific disk mount or service running on the system. I’m sure someone else can provide more benefits who use them in a production environment.
There is a tool named Podlet that can help translate to quadlets. I was able to fully translate my unraid and compose setups to quadlets.
It also can integrate with Systemd via Quadlets. Let’s you control containers as a sytemd service. I personally use them for my home server and have been happy with it.
That should be McDonald’s, not tacos on top. The taco is already on the bottom.
Stable distros are great as targets for development, such as for containers. It also works great for end user environments because developers aren’t trying to hit a moving target in terms of core libraries.
For a home user, having something more stable isn’t very beneficial. If you want to have things stay the same for the next 2 years or so, then go for it.
It’s one of the reasons why fedora works well, it has just a 6 month release cycle, so nothing gets too stale. More modern packaging formats like flatpak and appimage are changing things a bit since they don’t rely on the system packages and can use something newer.
No League of Legends either. Truly a wonderful system.



Selinux