Flatcar
os
Flatcar | os | |
---|---|---|
20 | 6 | |
631 | 688 | |
1.4% | 6.4% | |
7.5 | 10.0 | |
13 days ago | 7 days ago | |
Python | C | |
Apache License 2.0 | GNU General Public License v3.0 or later |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
Flatcar
- Linux fu: getting started with systemd
- Bottlerocket – Minimal, immutable Linux OS with verified boot
-
Wolfi: A community Linux OS designed for the container and cloud-native era
Sounds like you're looking for the CoreOS Linux successor FlatCar https://www.flatcar.org/
It's actually based on some ChromeOS update tools under the hood but is a regular Linux distro, just super minimal and designed to run containers.
-
Flatcar Container Linux
I guess if you found my comment to be "comically hyperbolic" then replying to mine with a "comically reductionist" is fair game
So, anyway, I actually did dig up a concrete example of my experience with it, and I cannot link to the "Additional information" section but that is both why I think the thing was a mess and also why the Miroservices YT joke resonated: https://github.com/flatcar/Flatcar/issues/220
I think the CoreOS boot strategy was decomposed into a bunch of different executables, each responsible for doing their own little slice of the world. Maybe it drew inspiration from systemd in that way. But, just like my real life experience with microservices, it requires keeping a bunch of different projects and their upgrade paths in ones head, knowing their disparate config formats, and when one of them inevitably has a bug, understanding how to troubleshoot what went wrong with the system as a whole
And, again in trying to be reasonable in this discussion[1] I do also understand why one would opt for the data URI, given how much of the rest of Ignition loads content from URLs. I don't believe cloud-init has that remote content paradigm baked into in nearly the same way, so I hear you about that.
And yes, my belief is that JSON is a data-exchange format from _computer to computer_ and making people write them is a poor DX choice, IN MY OPINION. And, to reiterate, I know that CoreOS's perspective is that it is a computer-to-computer transmission from the transpiler-project-o-the-day to the Ignition binary, but that is predicated on one having access to that transpiler binary in all cases, which is quite different from the problem that cloud-init is trying to solve
fn-1: I'm sorry you got hurt by my "tire fire" outburst, and that evidently derailed this whole interaction, but it was my experience
- An overview of single-purpose Linux distributions
- Linux Distro for Running Docker Containers in VM - Ubuntu, Alpine, or...?
os
- Chainguard Images now available on Docker Hub
-
Fat OCI images are a cultural problem
This is what the folks at Chainguard are solving with their Wolfi OS: https://github.com/wolfi-dev/os and tools like melange: https://github.com/chainguard-dev/melange
-
Wolfi: A community Linux OS designed for the container and cloud-native era
> OK: 9494 distinct packages available
I opened that apkindex file and it had duplicate entries for a ton of packages with different versions, taking a look at https://github.com/wolfi-dev/os I only see about 840 yaml files which I assume define the packages. I don't think claiming to have 10k packages when only 10% of them are actually different pieces of software is a good claim to make. Nixpkgs would have millions of packages if we added up every single unique package from every revision.
-
Fearless Distroless
Also check out the Chainguard Images, built on Wolfi: https://github.com/wolfi-dev/os
- Wolfi
-
Introducing Wolfi – the first Linux (Un)distro designed for securing the software supply chain
Source Link
What are some alternatives?
bottlerocket - An operating system designed for hosting containers
sbomnix - A suite of utilities to help with software supply chain challenges on nix targets
harvester - Open source hyperconverged infrastructure (HCI) software
wolfi-act - Dynamic GitHub Actions from Wolfi packages
talos - Talos Linux is a modern Linux distribution built for Kubernetes.
vulnerabilities - :rocket: A vulnerabilities database for fully-automated audits
typhoon - Minimal and free Kubernetes distribution with Terraform
images - Public Chainguard Images
elemental-toolkit - :snowflake: The toolkit to build, ship and maintain cloud-init driven Linux derivatives based on container images
attention-attention - Attention! Attention!
inspektor-gadget - The eBPF tool and systems inspection framework for Kubernetes, containers and Linux hosts.
pipeline - A cloud-native Pipeline resource.