<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Linux on Flatcar Container Linux</title>
    <link>/tags/linux/</link>
    <description>Recent content in Linux on Flatcar Container Linux</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <copyright>Copyright © The Flatcar Project Contributors.

Copyright © Flatcar a Series of LF Projects, LLC.

For website terms of use, trademark policy and other project policies please see &lt;a href=&#34;https://lfprojects.org/policies/&#34;&gt;lfprojects.org/policies&lt;/a&gt;.
</copyright>
    <lastBuildDate>Wed, 27 May 2020 08:00:00 -0700</lastBuildDate>
    <atom:link href="/tags/linux/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Container Linux: Back on Track with Flatcar</title>
      <link>/blog/2020/05/container-linux-back-on-track-with-flatcar/</link>
      <pubDate>Wed, 27 May 2020 08:00:00 -0700</pubDate>
      <guid>/blog/2020/05/container-linux-back-on-track-with-flatcar/</guid>
      <description>&lt;p&gt;Yesterday, CoreOS Container Linux reached its end of life (EOL). Today marks the beginning of Flatcar Container Linux as an independent Linux distribution. With this comes a certain responsibility, but more notably: an opportunity for Kinvolk and the broader container community.&lt;/p&gt;&#xA;&lt;p&gt;Just after the EOL announcement this February, Chris &#xA;&#xA;&#xA;&lt;a href=&#34;https://kinvolk.io/blog/2020/02/flatcar-container-linux-enters-new-era-after-coreos-end-of-life-announcement/&#34; target=&#34;_blank&#34; rel=&#34;noopener&#34;&gt;wrote a post&lt;/a&gt;&#xA; about what this would mean for Kinvolk and &#xA;&#xA;&#xA;&lt;a href=&#34;https://kinvolk.io/flatcar-container-linux&#34; target=&#34;_blank&#34; rel=&#34;noopener&#34;&gt;the Flatcar project&lt;/a&gt;&#xA;. Now that the end-of-life has come to pass, I’d like to build on Chris’ post, go further into where we go from here, and the reasons I’m excited to be at Kinvolk.&lt;/p&gt;</description>
    </item>
    <item>
      <title>VMware and Kinvolk bring Flatcar Container Linux to vSphere, providing supported path forward for CoreOS users</title>
      <link>/blog/2020/04/vmware-and-kinvolk-bring-flatcar-container-linux-to-vsphere-providing-supported-path-forward-for-coreos-users/</link>
      <pubDate>Tue, 21 Apr 2020 12:30:00 +0200</pubDate>
      <guid>/blog/2020/04/vmware-and-kinvolk-bring-flatcar-container-linux-to-vsphere-providing-supported-path-forward-for-coreos-users/</guid>
      <description>&lt;p&gt;Recently, we have been working with many end users who, faced with the imminent&#xA;end-of-life of CoreOS Container Linux, are migrating to Flatcar Container Linux&#xA;as the secure foundation for their container deployments. And, with the&#xA;majority of enterprises adopting vSphere for their private clouds&lt;sup id=&#34;fnref:1&#34;&gt;&lt;a href=&#34;#fn:1&#34; class=&#34;footnote-ref&#34; role=&#34;doc-noteref&#34;&gt;1&lt;/a&gt;&lt;/sup&gt;, we have&#xA;heard from many of those users that fully certified support for vSphere is an&#xA;important consideration in their migration decision.&lt;/p&gt;&#xA;&lt;p&gt;Today, we are pleased to share details of our collaboration with VMware to&#xA;enable the deployment of Flatcar Container Linux in a fully-supported vSphere&#xA;environment. There are a number of important elements to this:&lt;/p&gt;</description>
    </item>
    <item>
      <title>Steps to Migrate from CoreOS to Flatcar Container Linux</title>
      <link>/blog/2020/03/steps-to-migrate-from-coreos-to-flatcar-container-linux/</link>
      <pubDate>Wed, 18 Mar 2020 17:00:00 +0100</pubDate>
      <guid>/blog/2020/03/steps-to-migrate-from-coreos-to-flatcar-container-linux/</guid>
      <description>&lt;p&gt;&#xA;&#xA;&#xA;&lt;a href=&#34;https://www.flatcar-linux.org/&#34; target=&#34;_blank&#34; rel=&#34;noopener&#34;&gt;Flatcar Container Linux&lt;/a&gt;&#xA; is a drop-in replacement for CoreOS Container Linux. Thus, one should think that a migration should be an effortless task, and it is.&lt;/p&gt;&#xA;&lt;p&gt;Since Red Hat announced that &#xA;&#xA;&#xA;&lt;a href=&#34;https://coreos.com/os/eol/&#34; target=&#34;_blank&#34; rel=&#34;noopener&#34;&gt;CoreOS Container Linux will reach its end-of-life on May 26&lt;/a&gt;&#xA;, we’ve seen a major uptick in the usage of Flatcar Container Linux. We’ve also had a number of questions about the migration process. This post looks to highlight how to migrate to Flatcar Container Linux in two ways; modifying your deployment to install Flatcar Container Linux, and updating directly from CoreOS Container Linux.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Flatcar Container Linux enters new era after CoreOS End-of-Life announcement</title>
      <link>/blog/2020/02/flatcar-container-linux-enters-new-era-after-coreos-end-of-life-announcement/</link>
      <pubDate>Mon, 24 Feb 2020 12:10:00 -0700</pubDate>
      <guid>/blog/2020/02/flatcar-container-linux-enters-new-era-after-coreos-end-of-life-announcement/</guid>
      <description>&lt;p&gt;Almost two years ago, we launched &#xA;&#xA;&#xA;&lt;a href=&#34;https://www.flatcar-linux.org/&#34; target=&#34;_blank&#34; rel=&#34;noopener&#34;&gt;Flatcar Container Linux&lt;/a&gt;&#xA;, a drop-in replacement for CoreOS Container Linux. Since then, we’ve made almost 200 &#xA;&#xA;&#xA;&lt;a href=&#34;https://www.flatcar-linux.org/releases/&#34; target=&#34;_blank&#34; rel=&#34;noopener&#34;&gt;releases&lt;/a&gt;&#xA;, added an &#xA;&#xA;&#xA;&lt;a href=&#34;https://kinvolk.io/blog/2019/05/introducing-the-flatcar-linux-edge-channel/&#34; target=&#34;_blank&#34; rel=&#34;noopener&#34;&gt;experimental edge channel&lt;/a&gt;&#xA;, &#xA;&#xA;&#xA;&lt;a href=&#34;https://kinvolk.io/blog/2019/11/announcing-the-kinvolk-update-service-and-nebraska-project/&#34; target=&#34;_blank&#34; rel=&#34;noopener&#34;&gt;released the update server - Nebraska&lt;/a&gt;&#xA;, (re-)introduced ARM support (which had been dropped by Red Hat), and &#xA;&#xA;&#xA;&lt;a href=&#34;https://kinvolk.io/blog/2019/11/announcing-the-kinvolk-flatcar-container-linux-subscription/&#34; target=&#34;_blank&#34; rel=&#34;noopener&#34;&gt;introduced the Kinvolk Flatcar Container Linux Subscription&lt;/a&gt;&#xA;.&lt;/p&gt;&#xA;&lt;p&gt;But Flatcar Container Linux is about to enter a new era.&lt;/p&gt;&#xA;&lt;h2 id=&#34;the-new-era&#34;&gt;The New Era&lt;/h2&gt;&#xA;&lt;p&gt;Earlier this month, Red Hat announced the &#xA;&#xA;&#xA;&lt;a href=&#34;https://coreos.com/os/eol/&#34; target=&#34;_blank&#34; rel=&#34;noopener&#34;&gt;End of Life of CoreOS Container Linux&lt;/a&gt;&#xA; will be May 26th. This was something that had been expected since soon after the &#xA;&#xA;&#xA;&lt;a href=&#34;https://www.redhat.com/en/about/press-releases/red-hat-acquire-coreos-expanding-its-kubernetes-and-containers-leadership&#34; target=&#34;_blank&#34; rel=&#34;noopener&#34;&gt;CoreOS acquisition&lt;/a&gt;&#xA; was announced; everyone knew it was coming, but now we have dates.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Flatcar Linux is now open to the public</title>
      <link>/blog/2018/04/flatcar-linux-is-now-open-to-the-public/</link>
      <pubDate>Mon, 30 Apr 2018 12:00:00 +0200</pubDate>
      <guid>/blog/2018/04/flatcar-linux-is-now-open-to-the-public/</guid>
      <description>&lt;p&gt;A few weeks ago &#xA;&#xA;&#xA;&lt;a href=&#34;https://kinvolk.io/blog/2018/03/announcing-the-flatcar-linux-project/&#34; target=&#34;_blank&#34; rel=&#34;noopener&#34;&gt;we announced Flatcar Linux&lt;/a&gt;&#xA;, our effort to create a commercially supported fork of &#xA;&#xA;&#xA;&lt;a href=&#34;https://coreos.com/why/&#34; target=&#34;_blank&#34; rel=&#34;noopener&#34;&gt;CoreOS&amp;rsquo; container Linux&lt;/a&gt;&#xA;. You can find the reasoning for the fork in our &#xA;&#xA;&#xA;&lt;a href=&#34;https://www.flatcar-linux.org/faq/&#34; target=&#34;_blank&#34; rel=&#34;noopener&#34;&gt;FAQ&lt;/a&gt;&#xA;.&lt;/p&gt;&#xA;&lt;p&gt;Since then we&amp;rsquo;ve been testing, improving our build process, establishing security procedures, and talking to testers about their experiences. We are now satisfied that &#xA;&#xA;&#xA;&lt;a href=&#34;https://www.flatcar-linux.org/&#34; target=&#34;_blank&#34; rel=&#34;noopener&#34;&gt;Flatcar Linux&lt;/a&gt;&#xA; is a stable and reliable container operating system that can be used in production clusters.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Announcing the Flatcar Linux project</title>
      <link>/blog/2018/03/announcing-the-flatcar-linux-project/</link>
      <pubDate>Tue, 06 Mar 2018 17:05:56 +0200</pubDate>
      <guid>/blog/2018/03/announcing-the-flatcar-linux-project/</guid>
      <description>&lt;p&gt;Today Kinvolk announces &#xA;&#xA;&#xA;&lt;a href=&#34;https://flatcar-linux.org&#34; target=&#34;_blank&#34; rel=&#34;noopener&#34;&gt;Flatcar Linux&lt;/a&gt;&#xA;, an immutable Linux distribution for containers. With this announcement, Kinvolk is opening the Flatcar Linux project to early testers.&#xA;If you are interested in becoming a tester and willing to provide feedback, please &#xA;&#xA;&#xA;&lt;a href=&#34;https://docs.google.com/forms/d/1zferjzZGXN5p0B5tqUy19ye2Igwrgm-sS7Dly8jhb18/&#34; target=&#34;_blank&#34; rel=&#34;noopener&#34;&gt;let us know&lt;/a&gt;&#xA;.&lt;/p&gt;&#xA;&lt;p&gt;Flatcar Linux is a friendly fork of &#xA;&#xA;&#xA;&lt;a href=&#34;https://coreos.com/os/docs/latest/&#34; target=&#34;_blank&#34; rel=&#34;noopener&#34;&gt;CoreOS&amp;rsquo; Container Linux&lt;/a&gt;&#xA; and as such, compatible with it.&#xA;It is independently built, distributed and supported by the Kinvolk team.&lt;/p&gt;&#xA;&lt;h2 id=&#34;why-fork-container-linux&#34;&gt;Why fork Container Linux?&lt;/h2&gt;&#xA;&lt;p&gt;At Kinvolk, we provide support and engineering services for foundational open-source Linux projects used in cloud infrastructure.&#xA;Last year we started getting inquiries about providing support for Container Linux.&#xA;Since those inquiries, we had been thinking about how we could offer such support.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
