I mean isn't this, Lemmy, an answer as well?
andruid
There is always some solutionizm in tech, but I'm interested in containerzation as a solution to problems I've had with configure drift building up on my systems and make it easier to share and work with the community.
The immutable desktop work to me is specifically working on bridging the gap between the UX of a local admin (you know wanting custom configuration and fast reaction to user input) and the industrial expectations of being able to test and track every change and reduce the number of different pieces you need to operate a system.
Hopefully we can lose some of the industries bad habits though. Like "relying on this proprietary piece is ok because we can move faster" or making other excuses as if you are going to have to explain to your boss why some metric looks bad instead of just trying to make the best system or solution we can.
I love Linux gaming. Got the Steam deck for my SO. She kind of hates it BECAUSE it's not a no tinker device.
Like if you pick the right games you're good, but want to play the "wrong" game, or want to mod, and your back to tinkering.
I don't mind it at all, it's just what PC gaming has been for me my whole life, but for her, someone who only experienced gaming on newer consoles it's a pain in the tush.
Neat! What proccess did you follow for building distroless? I was using buildah, mounting dir, yum installing into the mount, and exporting that container off.
Heck you could even keep the hierarchy, but with no representation of the workers in leadership you lose an major perspective on the organization.
The fact that the employees were able represent their defacto power in a crisis is good, but the fact that the don't have explicit power in the decision making process is why this able to happen in the first place.
There are no good kings, even if the best men were made kings, they would be inherently tainted by the position.
No nix is super cool! I really like the idea that guix and nix in having that system as code from build to deployment. I am not sure yet on how I feel about it for fleet/cluster deployments, k8s schedulers, network patterns like service meshes, ETCD, and operating on labels and cluster state are all super powerful.
I have looked too into using nix to make OCI containers and OCI containers to make flatpaks as well. All where they make sense of course.
Containers are really awesome, but take a bit more to troubleshoot sometimes. Docker is not the only method to run them either. I prefer podman actually, but K3s is the next logical step for running services in a more powerful setup.
All true FOSS too
OpenQA is the best answer that I know of for this too! You can even trigger from Gitlabs CI jobs if you are already here.
On a similar note, I want to try boot2container as my PXE target next personally
Setup a good kickstart script (even if it's just enough for Ansible to Configure it the rest of the way). It's awesome when messing with a system to be able to reboot select the reinstall PXE boot option and get a fresh install to tinker on.
FSL is better than strait proprietary and if a company had to choose between the two I hope they choose FSL. All that said it just doesn't feel like there is a real hope here for the eventual Open source fork here. It's just a fail safe for people still on legacy systems and even then 2 years of potentially no new updates ... Could be killer for security flaws. With tons of paradigm shifts between then too.
It almost needs a SLA that says if it isn't maintained to a certain level then it is also opensourced.