8 ms·
Flatcar Container Linux
- quijoteuniv 4y ago«Flatcar Container Linux is maintained and developed by Kinvolk, a company that was acquired by Microsoft in 2021.»
- intelVISA 4y agoThanks for the warning, almost fell for it...
- jaboutboul 4y agoComments like this are unhelpful and unproductive. That team is totally independent and does some great work and has continued to be a totally community driven project.
- snerbles 4y agoSome people want to avoid tying their own projects to certain vendors, and this information is helpful to them. See also Oracle, IBM, etc. Microsoft has done quite a lot to rehabilitate their image, a decade ago few would be so quick to defend them.
- squarefoot 4y ago> Microsoft has done quite a lot to rehabilitate their image I don't want to sound as a anti-MS fanboy, but that's the standard procedure when you get to the point "If you can't beat them...". Microsoft isn't to be trusted just because they're a business, but because like many others they're after profits above anything else. Just look at how they turned a potentially very decent OS (Windows 7) into worse privacy nightmare at every new version. I simply don't want them to mess with Linux.
- snerbles 4y agoOh absolutely. Many of us remember EEE[0], but many more have forgotten - or never learned in the first place. [0] https://en.wikipedia.org/wiki/Embrace,_extend,_and_extinguish https://en.wikipedia.org/wiki/Embrace,_extend,_and_extinguis...
- sshine 4y agoI was recently forced to use Windows at work. I’ve since found a way to avoid that, but I did experience an ad pop-up before migrating to Linux. I can’t fathom how tech professionals can accept this kind of lack of control of their operating system.
- intelVISA 4y agoI appreciate where you're coming from but unfortunately I'm not able to support software that is backed by harmful corps like MS.
- sneak 4y agoAbsolutely not. When the paychecks come from a company that fundamentally does not believe in the four freedoms, that is critical information with regards to infrastructure. Free software is an ideology and philosophy, not just a license.
- prettyStandard 4y agoAgree with sibling comments. Not immediately relevant to me but at my current position we go out of our way to avoid anything and everything Amazon. Very hard to do. And if a project were backed by Amazon I would be very embarrassed to start building on it at work. We are so serious about this that I almost got a contract canceled because it looked like they were running on AWS, and we got them to switch to Azure.
- hughc 4y agoSibling comments are bashing MS. I read your comment to the end, and it read like a punchline to a joke, given who owns Azure?
- prettyStandard 4y agoI agree it does read like the punchline to a joke, that did not escape me when I wrote it, but the larger message is that comments explaining who really owns projects we're talking about are not "unhelpful and unproductive". Many of the sibling comments were coming from the maintaining freedom perspective, which I personally appreciate as well. I wanted to chime in that this information is also helpful from a corporate/competitive perspective.
- nelsonenzo 4y agoYeah, it's called the 'embrace' phase.
- t-lo 4y agoThe most significant change this acquisition brought to Flatcar was to turn it from a vendor-driven open source project to a community-driven one. Also see Kinvolk's statement at the time: https://kinvolk.io/blog/2021/04/microsoft-acquires-kinvolk/ https://kinvolk.io/blog/2021/04/microsoft-acquires-kinvolk/ Since then, the project has opened up and has become fully community driven - releases, features, stewardship, everything. To further underline independent stewardship, Flatcar was recently proposed to join the CNCF as an incubating project: https://github.com/cncf/toc/pull/991 https://github.com/cncf/toc/pull/991 .
- thrill 4y agoApplause to the group behind this. CoreOS "just the containers, ma'am" plus ChromeOS "set in stone" OS (but updateable) approach was so obviously good once you started using it that it was just begging to be picked up again.
- moduspol 4y agoSounds like k3os, although it kind of surprised me when k3os development was stopped. Agreed: something like this almost seems inevitable. When you just want Kubernetes, managing the underlying OS and packages just feels like a waste of time.
- trustingtrust 4y agoThere is one for arm64 is there one for the rpi4 ? I already run containers on mine this would be even better.
- blixtra 4y agoThis might help you: https://github.com/flatcar-linux/Flatcar/issues/502 https://github.com/flatcar-linux/Flatcar/issues/502
- moondev 4y agoThe rpi4 has uefi firmware available, this allows you to boot any generic uefi aarch64 image, you no longer need rpi specific images. https://github.com/pftf/RPi4 https://github.com/pftf/RPi4
- monocasa 4y agoIt still needs to be an RPi specific image on the card as this firmware lives on the sd card too.
- moondev 4y agoOne of the biggest advantages of the UEFI firmware is that you don't have to boot from the SD card. They are really unreliable and also awful for performance. USB3 or even netbooting are much better options.
- sisk 4y agoTo add, modern u-boot has enough UEFI support that you can get away with using it instead of this full tianocore-based implementation.
- t-lo 4y agoIt requires a tiny bit of messing around but yes, Flatcar runs on RPi. It's part of our docs; here's the howto: https://www.flatcar.org/docs/latest/installing/bare-metal/raspberry-pi/ https://www.flatcar.org/docs/latest/installing/bare-metal/ra...
- haarts 4y agoI've been reading a bit but it seems you can't add containers after you have booted the Flatcar distro. So define it on first boot or reinstall?
- blixtra 4y agoThis is incorrect. It’s an immutable OS. But containers can be started and stopped as much as you want. It’s the sole purpose of Flatcar.
- dilyevsky 4y agoNo not quite. You can even add new systemd units at boottime - there’s a special ignition config for that
- goombacloud 4y agoThere are multiple ways to start containers, one of them is to define systemd units in Ignition. If that part needs to change, reprovisioning is needed but a new "flatcar-reset" tool (in Alpha) should make the barrier for reprovisioning lower by only requiring a reboot and being able to keep wanted local data. In the past Ansible was a common choice if neither Kubernetes, Nomad or even docker compose are used.
- moondev 4y agoComparing Immutable infrastructure with cloud-init vs immutable filesystem with ignition. What advantages would flatcar provide.
- mdaniel 4y agoIgnition is a tire fire and I despise it with all my heart. It's made worse by there being like 5 different incompatible under-documented versions each with their own cutesy bugs In last contact I had with Flatcar (before we moved to Bottlerocket) one could still use cloud-init yaml even with Flatcar so that's what I'd recommend instead of trying to read through the unbounded number of github issues trying to track down why simple things don't work with ignition As for "what advantages Flatcar provides," the answer is always "in comparison to what?" I haven't run a general-purpose OS in production in over 8 years, and I don't intend to ever go back to having a mutable OS. There are just too many opportunities for randos to "just ssh in and do this one thing" and then I have to spend hours tracking down why some machines behave different from their peers
- pengaru 4y ago> Ignition is a tire fire and I despise it with all my heart. Could you elaborate on this? I helped [1] create Ignition with Alex Crawford [0], its original author, while @ CoreOS in ~2015. To call what we were making then a "tire fire" seems comically hyperbolic for what was such a rudimentary bootstrapping tool, and generally unexpected for something we'd ship. Has its scope grown out of control since those early days, or has it been mismanaged? We're coming up on a decade since my involvement... [0] https://github.com/coreos/ignition/commits?author=crawford https://github.com/coreos/ignition/commits?author=crawford [1] https://github.com/coreos/ignition/commits?author=vcaputo https://github.com/coreos/ignition/commits?author=vcaputo
- mdaniel 4y agoUltimately I'm sure I'm going to be sorry I weighed into this, because maybe it's just personal preference and I'm not going to change anyone's mind and you are unquestionably not going to get me to ever touch that again. And I'm sorry if your feelings are hurt, and I appreciate that you and your coauthor know and love the system but my experience with it mirrors that Microservices YouTube joke My biggest heartburn is that I have[1] to compile a boot configuration document. Some of that may be a concession to Ignition being inexplicably written in JSON, but it's possible the transpiler does some massaging and restructuring of keys, I dunno, I didn't want to compile a boot document This is how one creates a file in Ignition: https://coreos.github.io/ignition/examples/#create-files-on-the-root-filesystem https://coreos.github.io/ignition/examples/#create-files-on-... Contrast that with https://cloudinit.readthedocs.io/en/20.1/topics/examples.html#writing-out-arbitrary-files https://cloudinit.readthedocs.io/en/20.1/topics/examples.htm... I grant you that https://coreos.github.io/butane/examples/#files https://coreos.github.io/butane/examples/#files may be the example of pre-transpilation using the `inline:` structure but for my use case of authoring that UserData dynamically, I don't have a `!TranspileUsingCuteNameOfTheDay` in CloudFormation And since I haven't had my hands on the Flatcar ecosystem in a few years, I'm not going to have access to the very specific pain points of "well, this cutesy named thing is broken because it depends on this other cutesy named thing" but what it boils down to is cloud-init behaves sanely, has been around forever, and can be authored easily in a bunch of different circumstances fn-1: yes, I can appreciate it's "just a JSON document" but no reasonable person is going to author JSON string literals containing data: URIs for contents
- chubot 4y agoThis looks cool, but what's the dev environment like? I think Ubuntu is a popular base image in Docker because Ubuntu is popular for engineers to use on their desktops Debian usually passes for Ubuntu, since the package names are mostly the same. So either you do all your development in containers, or you have drift between the dev environment and the cloud.
- theodric 4y ago> Debian passes for Ubuntu Ubuntu passes for Debian, you mean. Debian has been around much, much longer than Ubuntu and set the standards Ubuntu got for free and commercialized.
- MathMonkeyMan 4y agoTrue, but devs like me started with Ubuntu. Then years later we see a Debian docker image and wonder how different it will be. Mostly the same, for the reason you mentioned.
- chubot 4y agoYes I know, but Ubuntu seems to be more popular as a desktop What I mean is that people just hack on stuff on their desktop. They install Python NumPy or Rails or whatever. Like gigabytes of dependencies. And then they want to deploy. Is it easy to do that with Flatcar Container Linux? How do I do it? Or is it easier to make a Docker file that does apt-get install X and pip install Y ? You can do that with Ubuntu as a base image, and Debian usually "just works" if you're on Ubuntu. (I'm doing this with our Debian CI images) Not saying you should always take the easier path, but I also think it's a good idea to minimize the differences between the dev environment and production
- dilyevsky 4y agoCool project. Also see https://getfedora.org/coreos?stream=stable https://getfedora.org/coreos?stream=stable for Fedora-based CoreOS successor
- pelasaco 4y agoor the openSUSE MicroOS https://microos.opensuse.org/ https://microos.opensuse.org/
- seized 4y agoFedora IoT is an easy step to this as well. It's really "Silverblue server", rpm-ostree based but without making the jump to ignition files right away.
- dilyevsky 4y agoat least to me the declarative setup of ignition was the selling point, not the rpmostree (altho it is nicer than dnf/old school rpm). Another cool thing about fedora-based is that it seems much more bleeding edge in terms of kernel version on other os packages than chromiumos which is what I want for immutable infrastructure
- t-lo 4y agoFor more on immutable / image-based Linux you might want to check out the UAPI group, a recently founded cross-distro interest group: https://uapi-group.org/ https://uapi-group.org/ We have contributing members from many FOSS projects gravitating around image-based Linux, including quite a few distros.
- Erlangen 4y agoIs this a fork and continuation of coreos? Tracking down the git log, a lot of commits were made by coreos and redhat employees.
- vxNsr 4y agoAppears to be a continuation of that project under a different name. Someone else pointed out that this one was acquired my Microsoft in 2021, but does appear to be receiving regular updates so it’s not sunsetted yet.
- brancz 4y agoYes this is a direct fork. I happened to have been a CoreOS Berlin employee and know the kinfolk folks (now acquired by Microsoft) that did this fork after the Red Hat acquisition very well. I’m very glad they did, a lot of things I liked a lot about CoreOS container Linux unfortunately didn’t make it into Fedora CoreOS. The kinfolk folks also run the update server to perform auto updates. //edit Continuation wouldn’t be a wrong word either as it all coincided with the Red Hat acquisition. But I guess “fork” is correct since it’s under a different name.
- avtar 4y ago> a lot of things I liked a lot about CoreOS container Linux unfortunately didn’t make it into Fedora CoreOS. Like what?
- brancz 4y agoA couple of small things, but primarily I don’t think it actually embraced immutability in the same way. CoreOS container Linux used A/B partitions for updating truly immutably. Partition B didn’t boot? Just boot A again. Fedora CoreOS and RHEL CoreOS use OSTree [1], no shade on OSTree, it works well, but I slept better with A/B partitions, I just find them easier to reason about. [1] https://github.com/ostreedev/ostree https://github.com/ostreedev/ostree
- 4y ago
- kris-nova 4y agoHow does this compare to https://ublue.it/ https://ublue.it/
- jcastro 4y agoublue is based off of fedora and rpm-ostree, which is what "CoreOS" is today. What happened was old school CoreOS was A/B partition based: https://github.com/coreos/docs/blob/master/os/sdk-disk-partitions.md https://github.com/coreos/docs/blob/master/os/sdk-disk-parti... My memory is hazy but here's how I remember it: After Red Hat acquired CoreOS they announced their intent to rebase the entire thing around rpm-ostree, which is the CoreOS people know today: https://coreos.github.io/rpm-ostree/ https://coreos.github.io/rpm-ostree/ At the time there was some anxiety in the community as to what would happen, as there was no direct upgrade path from old CoreOS to new CoreOS. Theoretically if we all believed the kool-aid we were drinking it's just a redeploy, no pets! Kinvolk came along, forked it, and made Flatcar Linux, which kept the A/B partitioning system, and more crucially, let you just change a config file and all your old CoreOS nodes would just move to Flatcar and then you were good to go. So now if you wanted to stay on the system you were comfortable with you could just use Flatcar. If the composability of rpm-ostree attracted you then new CoreOS have you covered. Red Hat deserves a hat tip here because in their documentation/blog they explicitly mentioned Flatcar as an option for people who wanted to stick with what they know, which I thought was cool and how I discovered it! Later on Microsoft acquired Kinvolk and and then people raised eyebrows. I have not checked in a while but the folks involved continued to do their thing and run it like a good OSS project, hold public meetings, all that stuff. Microsoft gets a good hat tip here. I use both and they're both high quality.
- nimbius 4y agoKinda related, but a flatcar was historically a kind of railcar you could mount shipping containers, chassis and large +100 short ton loads onto. These days we call them intermodal frames or an intermodal chassis. It can go from rail to cargo ship to truck to plane, and its all highly standardized and scalable :) CSX even uses them to test their robotic conductor/ automated locomotive technology
- PuffinBlue 4y agoThey mention the name association in the FAQ. [0]https://www.flatcar.org/faq#what-is-the-significance-of-the-flatcar-container-linux-name https://www.flatcar.org/faq#what-is-the-significance-of-the-...
- mixdup 4y agoI mean flatcars are still used today (not just historically) for things like tanks, farm equipment, lumber, semi-trailers, and sometimes even standard containers (https://en.wikipedia.org/wiki/Flatcar https://en.wikipedia.org/wiki/Flatcar) Cars that carry containers are now mostly referred to as well cars (https://en.wikipedia.org/wiki/Well_car https://en.wikipedia.org/wiki/Well_car) An intermodal chassis or frame usually refers to the highway version used to pull a container behind a truck (https://en.wikipedia.org/wiki/Container_chassis https://en.wikipedia.org/wiki/Container_chassis)
- i-das 4y agoHow is this different from Fedora Sliverblue ( https://silverblue.fedoraproject.org/about https://silverblue.fedoraproject.org/about ) ?
- queil 4y agoSilverblue is meant for desktop whereas flatcar is for running production workloads (like a server for containers).
- wejick 4y agocould anyone explain where do you use flatcar? is it a distro where people build container like alpine or a distro to run containers? What's the upside of using flatcar or coreos compared to (say) ubuntu server?
- t-lo 4y agoIt's a distro to run containers on. It is configured declaratively before deployment, so there's no config drift. It's fully automatable and the OS is self-updating (atomically, including automated roll-backs to known-good states). The OS cannot be extended after provisioning and all its binaries reside on a read-only partition (under /usr). Updates always replace the whole OS partition (though roll-back is possible). The root remains writable so users can add containerised apps and services etc. Think of it as rather strong separation between operating system and user-defined workloads (containerised apps, Kubernetes, etc.). For a (very) lightweight hands-on intro check out https://www.flatcar.org/docs/latest/installing/ https://www.flatcar.org/docs/latest/installing/ .
- yuriy-yarosh 4y agoI'm working on a AWS Bottlerocket remix with self-hosted capabilities and Azure/GCP support, and we're planning to release it for a ready to use opinionated CNCF stack Kubernetes distro (about 40 different tools), similar to VMWare Tanzu and RedHat's OpenShift. We were facing a lot of controversy behind Flatcar already - there's no clear Licensing policy for their "Fully OpenSource" release. Kinvolk should've prepped at least a License matrix of what's been hacked out of CoreOS - what is actually behind their "Pro Features" and how exactly it is "Fully Open Source". "Flatcar Linux Pro Features", in terms of "Linux Kernel Optimization', "GPU instances support" with "Accelerated Networking", are Not So Pro, and are something that everyone use on a daily basis. So, just from pure Support Monetization perspective, it's impossible to use Flatcar Linux reliably for Free (mic drop).
- blixtra 4y agoThanks for dropping the mic, I'll kindly pick it up. I'm the initiator of the Flatcar Container Linux project and former CEO of Kinvolk. Thus, I'm rather knowledgeable about the project and was involved in most decisions. The controversy you speak of is very new to me. If you could point to any references, I'd love to be aware of them. Firstly, there was nothing "hacked" out of CoreOS. Flatcar is literally the CoreOS Container Linux repos forked and carried on as is. Once the CoreOS EOL was reached we started updating the stale packages. That's it. Any further updates are what any distro would do in the course of maintenance to remain modern and relevant. Secondly, anything that was previously termed the "Pro" version is now just available in the standard version. So there is no difference. To my knowledge, the project doesn't even produce any Pro versions any longer and I don't think there are even any references to it in our docs. But even when we did have a Pro version, all the work we did was done in the open and was in our source repositories. We just didn't release public builds of those. Unlike CoreOS, we also developed* and open sourced the update server. It's called Nebraska and available here under an Apache license. https://github.com/kinvolk/nebraska https://github.com/kinvolk/nebraska With regard to a license matrix, you can find all licenses for each release in the respective release directory. For example this one: https://stable.release.flatcar-linux.net/amd64-usr/current/flatcar_production_image_licenses.json https://stable.release.flatcar-linux.net/amd64-usr/current/f... If you do find anything that is not 100% open source, let me know and I'll follow up to make sure that's corrected. I'm happy your excited about your project. But I think you'll fine it's better in the open source space to compete on merit and form relationships rather than tear down other projects and the work of the people behind the projects. * based on the Core Roller project: https://github.com/coreroller/coreroller https://github.com/coreroller/coreroller
- 3np 4y agoFrom the front-page: > The Kinvolk Update Service allows for defining instance groups, assigning update channels and controlling the frequency, time of day and rate of updates. What is this? From a quick glance I don't see it mentioned elsewhere. A hosted service? Something with a different license?
- blixtra 4y agoThe update server supports the Omaha protocol, is called Nebraska and is available here under an Apache license: https://github.com/kinvolk/nebraska https://github.com/kinvolk/nebraska Our team hosts the public server, but any Flatcar user can run Nebraska themselves and point their nodes to that.
- t-lo 4y agoThanks for the feedback :) Apparently there's always room to improve our docs. A maintainer has taken a stab on that (see https://github.com/flatcar/flatcar-website/pull/263 https://github.com/flatcar/flatcar-website/pull/263 for progress) and we'll update our docs shortly.