rpm-ostree is the hybrid image/package system that provides transactional upgrades on Atomic Host. Here are some highlights from version v2017.8, including better PolicyKit integration and support for RPM file triggers.
Project News
Fedora 26 Atomic Host September 05 Release
A new Fedora Atomic Host update is available via an OSTree commit:
Commit: 0b0127864022dd6ffad1a183241fbd5482ef5a1642ff3c8751c2e6cae6070b1a
Version: 26.120
Note that the issue which prevented specific hardware platforms from booting is now fixed in this release.
Running Kubernetes on Fedora Atomic Host
Fedora 26 Atomic Host relies on Kubernetes for automating deployment, scaling, and operations of application containers across clusters of hosts.
Getting up and running with Kubernetes on Fedora Atomic Host involves installing Kubernetes (or sticking with the version of the software that’s currently baked into the images), and then configuring a cluster. This can be done manually, with the Kubeadm utility, or with Ansible scripts (among other methods).
Fedora Layered Image Release August 2017
The Fedora Atomic WG and
Fedora Release Engineering teams have updated the Fedora Layered Image Registry. With this latest release, images based on Fedora 26 are now available, in addition to the images which were already available based on Fedora 25. This update also includes fedora-minimal
images for all active releases, each containing a stripped-down version of Fedora at about 100MB in size.
Fedora 26 Atomic Host August 22 Release
A new Fedora Atomic Host update is available via an OSTree commit:
Commit: 13ed0f241c9945fd5253689ccd081b5478e5841a71909020e719437bbeb74424
Version: 26.110
Warnings
Hardware Issue: During our testing phase we found an issue where on a specific hardware platform we could not boot after installing from the ISO images, or after updating to this release. If you experience similar behavior please use the previous ISO image. For existing machines, users with affected hardware should either wait for the next two-week release to upgrade, or switch to the updates ref where the issue is already fixed.
Kubernetes: We have also been notified by users that there are firewall issues with Docker 1.13 and Kubernetes.