Announcing new releases Beta 4722.1.0, Stable 4593.2.4, LTS 4081.3.9

1 view
Skip to first unread message

Flatcar Container Linux User

unread,
Jul 9, 2026, 10:52:38 AM (9 days ago) Jul 9
to Flatcar Container Linux User

Hello,

We are pleased to announce a new Flatcar Container Linux release for the Beta, Stable, and LTS channel.

New Beta Release 4722.1.0

Changes since Beta 4694.1.0

Security fixes:Bug fixes:
  • Fixed booting the VirtualBox image, which was broken since upstream Ignition changed how their VirtualBox support works. The Vagrant VirtualBox image was unaffected.
  • Fixed using Ignition to create new partitions with number 0 to get the next available slot. (ignition#2234)
  • Updated the GCE udev disk rules to include NVMe disks. (scripts#3606)
Changes:
  • Exoscale: images are now built as 10G .qcow2 so they can be directly used with Exoscale Custom Templates (scripts#4075)
  • Added Oracle Cloud Infrastructure images (scripts#3846)
  • Added kernel config options to support HuC firmware authentication which is required for Intel Arc (DG2) hardware offloading for video. (scripts#4019)
  • All the legacy OEMs (CloudSigma, CloudStack, Exoscale, Vagrant, VirtualBox) have been converted to sysexts. The transition should be seamless, but the Flatcar team was only able to test VirtualBox with and without Vagrant, so please report any issues.
  • Dropped support for Equinix Metal (Packet). The servers are due to be switched off on June 30th 2026.
  • Dropped support for Rackspace, including OnMetal. Rackspace-specific images are no longer built or published. Flatcar only had community level support for Rackspace, and the Flatcar team is no longer confident that this support actually works. Rackspace themselves have pivoted from being an independent cloud provider to being a management platform for other clouds.
  • Dropped the VMware "insecure" image. This was added a long time ago, and it is not clear to the current Flatcar team what purpose it served. It included the Vagrant insecure SSH key but without the other Vagrant files. If you want to use Vagrant, then do so with VirtualBox or Parallels. If you want to deploy onto VMware quickly, then use the OVA image.
  • Dropped the Vagrant VirtualBox image because the regular Vagrant image also targets VirtualBox. The only difference between them was that the former was geared for provisioning with Ignition and Afterburn rather than cloud-config and Vagrant itself. The Ignition support was broken when it was dropped by upstream. A single image can handle Ignition, cloud-config, and Vagrant. The Afterburn support has been dropped entirely.
  • Refreshed the Vagrant and Vagrant Parallels images for use with recent Vagrant releases, adding implicit support for provisioning with Ignition (VirtualBox only) or cloud-config. Vagrant 2.2.5 is now required. See the revised documentation for further details.
  • Refreshed the VirtualBox OVF (which is also used by the Vagrant image) so that VMs are configured with modern hardware, including a VirtIO storage controller and UEFI. The clock is configured for UTC rather than local time.
Updates:

Changes since Alpha 4722.0.0

Security fixes:Updates:New Stable Release 4593.2.4

Changes since Stable 4593.2.3

Security fixes:Updates:New LTS-2024 Release 4081.3.9

Changes since LTS-2024 4081.3.8

Security fixesUpdates:

Best,
The Flatcar Container Linux Maintainers

Reply all
Reply to author
Forward
This conversation is locked
You cannot reply and perform actions on locked conversations.
0 new messages