7 ms·
Wolfi: A community Linux OS designed for the container and cloud-native era
- eptcyka 3y agoWhat does un-distro mean?
- magicalhippo 3y agoThink of a circle with a fine split in it. At one end there's using a distro. You go around the circle to distroless, and on the other end of the circle, close to using a distro, but not using a distro, is un-distro. Paraphrased in jest from https://www.youtube.com/watch?v=_OEO79B-CZ4 https://www.youtube.com/watch?v=_OEO79B-CZ4 Seems they use it to highlight it's not just distroless but also kernel-less[1]. [1]: https://www.chainguard.dev/unchained/introducing-wolfi-the-first-linux-un-distro https://www.chainguard.dev/unchained/introducing-wolfi-the-f... (last section)
- dlor 3y agoIt was meant to be a tongue-in-cheek way of pointing out that a it's a Linux distro without the Linux kernel, so it's really an "unLinux distro", or an (un)distro for short.
- eptcyka 3y agoThe last section in the link helped, but I have to say, the circle analogy made very little sense to me. Thank you for clarifying nonetheless.
- magicalhippo 3y ago> the circle analogy made very little sense to me Yeah, was just a silly connection I made to the sample used in the track[1]. From a documentary on LSD[2]. [1]: https://www.psydb.net/release/hallucinogen-the-lone-deranger/6445 https://www.psydb.net/release/hallucinogen-the-lone-deranger... [2]: https://www.youtube.com/watch?v=gm6-THvnf44 https://www.youtube.com/watch?v=gm6-THvnf44
- mkl 3y agoSeems to have a confusing lack of "getting started" documentation. On the plus side, I now know what the world's smallest octopus is, so the important stuff is covered!
- denhamparry 3y agoI'm thankful that the important stuff is covered , there is helpful documentation over here btw https://edu.chainguard.dev/open-source/wolfi/overview/ https://edu.chainguard.dev/open-source/wolfi/overview/
- raybb 3y agoThey should probably have it linked in the readme but this is their getting started guide: https://edu.chainguard.dev/open-source/wolfi/wolfi-with-dockerfiles/ https://edu.chainguard.dev/open-source/wolfi/wolfi-with-dock...
- aerfio 3y agoFrom my side I'd love to see clear comparison to distroless[1] images, the best info I could find was this Github issue comment[2], although I would expect to find it in https://github.com/wolfi-dev#faq https://github.com/wolfi-dev#faq. Or maybe my google-fu failed me :( [1]: https://github.com/GoogleContainerTools/distroless https://github.com/GoogleContainerTools/distroless [2]: https://github.com/tektoncd/pipeline/issues/5507#issuecomment-1249368724 https://github.com/tektoncd/pipeline/issues/5507#issuecommen...
- dlor 3y agoI was (one of) the original creators of the Google Distroless project. The main difference is that Original Distroless uses Debian as the upstream. This is great in many ways, but makes it so stuff outside of Debian is hard to package in. Wolfi is its own upstream - packages are sourced and built directly from source, without another Linux distro. The rest of the differences stem from here - we get more control over what we package and how, and are able to more quickly add new versions of packages, or roll out CVE patches.
- iamstan23 3y agoNot sure an OS created to meet the specific need of VC funded startup, created exclusively by employees of that company should be called a "community Linux". It's almost the opposite of that in fact.
- amouat 3y agoYou're welcome to join the regular community meeting: https://github.com/wolfi-dev/community https://github.com/wolfi-dev/community We do fully intend for wolfi to be a community project, but it will take some time. We do say on the home page: >What are the plans for long-term Wolfi governance? We intend for Wolfi to be a community-driven project, which means over time it will have multi-vendor governance and maintainers. For now we're focused on building the project and community, and will revisit this in several months when a community has formed.
- k1rby 3y ago++the next call is July 5th at 12 pm EST. Come with questions! Here is the direct link to the public calendar :o) https://www.google.com/calendar/event?eid=aWpydnZxc2VhaHBlMzY5OWIzN2xvdGJmYXZfMjAyMzA3MDVUMTYwMDAwWiBjXzdlYzYwZjQ4NTkzMWY5MDU2MDQwYTNlMjQyNzM0MDBkZTQxYTE0M2VjNjA3MDNiNDExZDc3YjFmNTM0ZWMxNWZAZw&ctz=America/Chicago https://www.google.com/calendar/event?eid=aWpydnZxc2VhaHBlMz...
- dlor 3y agoTotally understand the concern. We've tried to draw a very clear line between Wolfi (the project), and Chainguard Images (our product). They're in different GitHub organizations, have different maintainers, and are documented differently. We (Chainguard) still represent most of the maintainers to Wolfi, but there are external folks too. We're going to need help scaling Wolfi to get it to where we want it to be, and that will require a real community. We've also tried to be very clear on the business model for us, to avoid any "rug pulls" or "bait and switches" later. Here's some more context on that too: https://www.chainguard.dev/unchained/scaling-chainguard-images-with-a-growing-catalog-and-proactive-security-updates https://www.chainguard.dev/unchained/scaling-chainguard-imag...
- rcarmo 3y agoI like the idea of having an SBOM as a standard, baked-in feature from the outset. That kind of thing is becoming critical in software supply chain management.
- dlor 3y agoThanks! By building the SBOMs as part of the build process we can ensure full coverage, vs. the other approaches that rely on "guessing" the contents after. We wrote a bit more about this approach here: https://www.chainguard.dev/unchained/make-sboms-not-guessboms-why-we-need-to-shift-left-on-sbom-generation https://www.chainguard.dev/unchained/make-sboms-not-guessbom...
- schemescape 3y agoIf nothing else, it's at least useful to ensure you are able to comply with all the open source license terms. Now how many copies of the MIT and BSD licenses do I need to include with my software? ;)
- thomasfromcdnjs 3y agoWhat is the benefits of using the container kernel? Does alpine generally do this if it installed in a container?
- dlor 3y agoYou don't really have a choice - containers always use the host kernel. So packaging the full kernel itself is a waste of space at best, confusing to CVE scanners, and something you just don't need to bother with if you work with containers only.
- jaboutboul 3y agoWhile I do appreciate the great work than Dan and team do, I feel like posting this headline, at this time, is click-baiting and playing off the recent Red Hat shake up to try and grab attention.
- dlor 3y agoThe fun part of HN is that you don't get to pick your turn on the front page. This was a surprise to me too, but I'm guessing it's up here for the same reasons you are.
- nine_k 3y agoIs this the first and only submission about Wolfi? It may just enjoy traction because of the recent news. Also, posting and upvoting timely and relevant links is something that makes HN valuable, among other things.
- pbronez 3y agoWhat’s the new news? The last major RedHat drama I’m aware of was the CentOS shakeup.
- pbronez 3y agoAh, they changed RHEL Source visibility from Public to subscribers only to make it harder for Rocky Linux, et al to provide strong compatibility. Lame. https://www.phoronix.com/news/Red-Hat-CentOS-Stream-Sources https://www.phoronix.com/news/Red-Hat-CentOS-Stream-Sources
- kristianpaul 3y agoDistroless or not, maintainers are required… but for me running docker pull debian still does the job. Whats wrong with current distros vuln assesment and security reporting to have another one?
- dlor 3y agoDebian does a great job! But here's one example where their packaging system makes container workloads hard. Debian, like many other distros has a strict "one version of every package" rule, meaning that Debian only ships one version of common things like programming languages or webservers. If you "apt-get install nodejs", you can only have Node.js v18, in the very very recently released Debian bookworm. If your devs need Node.js v20, or even v22 which will both be LTS releases during the bookworm release cycle, you're out of luck. You can go install those outside of the Debian package manager, but then you're on your own for vuln assessment and security fixes. Worse - many scanners don't actually even "see" packages that are installed outside of package managers, so you may not know that these exist or are installed. We designed Wolfi to be more flexible around package versions. This is a very very hard problem to solve in general, but since we're focused on immutable containers, we can skip a lot of the complexity around conflicts, upgrade/downgrade scenarios, and cross-version compatibility.
- Gasp0de 3y agoIf I need node.js 20 I will just use the node:20-bookworm image.
- dlor 3y agoAnd the fun part there is that this image is effectively a workaround - node.js 20 is installed via curl | bash. That means CVE scanners and SCA tools can miss node itself in that image. As silly as it sounds, try running "snyk container test --print-deps" on that image, and look around for Node. This approach works fine, but means that you might not be able to rely on most container security scanners to let you know when there's an issue.
- abrookewood 3y agoWasn't really sure where this was going, but the background to this approach adds some details - namely what they mean by distro-less and how they pull it off. https://www.chainguard.dev/unchained/minimal-container-images-towards-a-more-secure-future https://www.chainguard.dev/unchained/minimal-container-image...
- SamuelAdams 3y agoWe use Alpine Linux in all our docker builds for AWS ECS / Fargate. I noticed the FAQ says this: > Wolfi is a Linux undistro designed from the ground up to support newer computing paradigms such as containers. Although Wolfi has a few similar design principles as Alpine (such as using apk), it is a different distribution that is focused on supply chain security. Unlike Alpine, Wolfi does not currently build its own Linux kernel, instead relying on the host environment (e.g. a container runtime) to provide one. Is it possible to expand on this more? Why should I, a technical expert, use this over an already established distribution (Alpine)? What are good talking points I can bring to management / architects that would sell them on a switch? Can you expand on what “supply chain security” actually means?
- dlor 3y agoIn this case, supply chain security mostly means compliance. Alpine and other distros already do a great job at most aspects of supply chain security, but we make package/image signatures and SBOMs very easy to get in Wolfi. We're also more flexible on packaging extra software in Wolfi than other distros are, which has an effect on your overall supply chain security posture. We're aiming to package the entire Cloud Native landscape (to start!), so you can simply "apk add" anything you need, without having to drop back to "curl | bash" in your Dockerfile. By making it easier for devs to get the software they need "the right way", they'll have a reduced need to work around the already existing secure distribution mechanisms built into their distros. If you're already on Alpine and like it, that's great! If there are some packages you can't find in Alpine, or musl vs. glibc ever causes you issues, or you need SBOMs for some reason, give Wolfi a try!
- SamuelAdams 3y agoI’ve worked in a few industries that were crazy about compliance. Do you have any certifications for different compliances? Ie FedRamp, IL4/5/6, HIIPA, etc. I don’t think any other container images are strictly compliant with these standards - they’re not certified, but the technology stack (ECS, EKS, etc) is certified. Either way, if you can get this certified with different compliance platforms that would be a big selling point for B2B customers.
- fesc 3y agoWhat the hell is an OS without a kernel? Is this less an OS and more like a toolchain to build container images?
- amouat 3y ago99% of Wolfi is the package repository. We've compiled all the software to run an OS from source against glibc and made it available as APKs (apart from the kernel). The major use case for this is composing container images using tools like apko. When you run Linux containers, you're using the kernel from the host, but everything else is provided in the container i.e. file system, utilities etc. So you can effectively run Debian or Alpine on top of a Arch kernel by just doing "docker run debian" etc. And now you can also do "docker run cgr.dev/chainguard/wolfi-base".
- jmakov 3y agoWhy would I use that instead Clear Linux?
- dlor 3y agoWolfi is for running inside the container instead of on a VM or bare metal host. They're complementary - you'd run something like Clear Linux to boot up into a container host, then run this inside the containers.
- xnyanta 3y agoI've attended a local CNCF meetup where the chainguard folks presented Wolfi and their related tools to create container images and SBOMs. I was already skeptical of the product, having heard of it before. Unfortunately, attending that talk confirmed to me that they've just re-invented a severely limited version of Nix powered by yaml files that can output SBOMs in a standard format. Their software repository only has around 500 packages vs the 80k+ in nixpkgs. When I read "Alpine Linux", I was immediately reminded of its use of the musl libc which has endless DNS resolution issues[1][2] in and outside of Kubernetes, however, thankfully, it seems like they realized bundling musl was a bad idea and ship glibc instead. I'll stick to Nix and nixpkgs to build my reproducible container images with full dependency graphs back to the source code. 1: https://martinheinz.dev/blog/92 https://martinheinz.dev/blog/92 2: https://news.ycombinator.com/item?id=35058094 https://news.ycombinator.com/item?id=35058094
- dlor 3y agoWe're rapidly approaching 10k packages, here's today's count: / # apk update fetch https://packages.wolfi.dev/os/aarch64/APKINDEX.tar.gz https://packages.wolfi.dev/os/aarch64/APKINDEX.tar.gz [https://packages.wolfi.dev/os https://packages.wolfi.dev/os] OK: 9494 distinct packages available We're definitely coming at this from a different angle from Nix, but the approaches are pretty complementary. I'm a big fan of all the work they do. musl vs. glibc is one of the big departures we make from Alpine though, we use glibc everywhere because of those issues you pointed out.
- xnyanta 3y ago> 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 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.
- 3y ago
- JeremyNT 3y agoTo save some people a click, the headline made me assume this was something like CoreOS, but this is in fact the opposite. It's not a traditional Linux distro you can actually run standalone, it's just another base for building OCI containers.
- amouat 3y agoYeah, it's definitely not a platform for running containers. Apologies for any confusion there. But regarding being a full linux distro, we're really just missing the kernel and I could see that happening at some point in the future.
- 0xbadcafebee 3y agoThey could've just improved Alpine's supply chain (or built on top of it) rather than making a new distro :( But they're a company, so pushing out new products faster is more important than the community.
- dlor 3y agoWe work with much of the Alpine community and some of the maintainers. The glibc choice instead of musl alone means that a separate toolchain and distro is required, but there are also a lot of other distinctions. We still work with them upstream on apk and apk-tools, and would be happy to collaborate on more tooling.
- ariadneconill 3y agoWe have contributed the majority of our improvements in such a way that other APK distributions, including Alpine, can make use of them, and the original plan was to just leverage Alpine for all of this. Indeed, we even sponsored the refactoring of musl's DNS implementation that allows it to support DNS over TCP now. But we heard overwhelming demand for glibc support from customers. So we built a companion distribution for customers who needed to run GNU/Linux workloads, but still wanted to leverage the advantages of Alpine.
- p4bl0 3y agoBefore reading the linked page, I thought this was about a Linux distribution optimized to run both local but containerized applications and remote/cloud web applications, kind of a ChromeOS like distribution with the same focus on simplicity and security, but with an addition local execution approach based on containers, and less tied to Google. So, this is not at all this, but now I wonder if a distribution like the one I imagined exists?
- robszumski 3y agoSounds like you're looking for the CoreOS Linux successor FlatCar https://www.flatcar.org/ 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.
- GordonS 3y agoVMware's PhotonOS is designed for use as a stripped-down container host. It's pretty good, and they're open to community contributions too.
- mdaniel 3y agoTo add to the other excellent answers, I would recommend adding Bottlerocket to your reading list: https://github.com/bottlerocket-os/bottlerocket#readme https://github.com/bottlerocket-os/bottlerocket#readme I'm also aware of (but haven't used) https://github.com/siderolabs/talos#readme https://github.com/siderolabs/talos#readme I just realized your question may have implied a desktop os, whereas Bottlerocket, Flatcar, and likely the others in this specific thread are server-side. I don't have much experience with trying to solve that problem on the desktop except for the horror-show that is snap