Fedora project developers about the start the first preliminary version of the new distribution edition , which replaces the Fedora Atomic Host and CoreOS Container Linux products as a single solution for running environments based on isolated containers.
From CoreOS Container Linux, which was acquired by Red Hat after purchasing the CoreOS company, Fedora CoreOS incorporates deployment tools (configuration system at the initial boot stage using Ignition), atomic update mechanisms, and the overall product philosophy. From Atomic Host, it has adopted package management technology, support for OCI (Open Container Initiative) specifications, and additional container isolation mechanisms based on SELinux. The foundation of Fedora CoreOS is built from Fedora repositories using rpm-ostree. For container runtimes supported in Fedora CoreOS, Moby (Docker) and podman are mentioned. Support for container orchestration using Kubernetes is planned on top of Fedora CoreOS.
The project aims to provide a minimal environment that is atomically updated automatically without administrator intervention and uniform for mass deployment of server systems intended solely for running containers. Fedora CoreOS includes only a minimal set of components necessary for executing isolated containers — a Linux kernel, the system manager systemd, and a set of utility services for SSH access, configuration management, and update installation.
The system partition is mounted in read-only mode and is not changed during operation. is passed at boot time using Ignition tools (an alternative to Cloud-Init).
Once the system is up and running, changing the configuration and contents of the /etc directory is impossible; only the settings profile can be modified and used to replace the environment. Generally, working with the system resembles working with container images that are not updated in place but are rebuilt from scratch and restarted.
The system image is indivisible and is created using OSTree technology (individual packages cannot be installed in such an environment; the entire system image must be rebuilt, expanding it with new packages using the rpm-ostree tool). The update system is based on using two system partitions, one of which is active while the other is used for copying the update. After the update is installed, the roles of the partitions are switched.
Three independent branches of Fedora CoreOS are offered:
testing with snapshots based on the current Fedora release with updates; stable — the stabilized branch, created after two weeks of testing the testing branch; next — a snapshot of the upcoming release under development. Updates addressing vulnerabilities and serious bugs are provided for all three branches. At this stage of development, only the testing branch is being formed within the preliminary release. The first stable release is planned for six months from now. Support for the CoreOS Container Linux distribution will be discontinued six months after the stabilization of Fedora CoreOS, while support for Fedora Atomic Host is expected to end in late November.
After stabilization, telemetry sending will be enabled by default (in the preliminary build, telemetry is currently inactive) using the fedora-coreos-pinger service, which periodically collects and sends to the Fedora project servers non-identifying information about the system, such as the OS version number, cloud platform, and installation type. The data transmitted does not contain information that could lead to identification. Only aggregated information is used for analyzing statistics to generally assess the usage patterns of Fedora CoreOS. Users can disable telemetry sending or extend the default transmitted information if desired.
Source: opennet.ru
