{"id":55313,"date":"2020-01-17T00:00:00","date_gmt":"2020-01-16T21:00:00","guid":{"rendered":"https:\/\/prohoster.info\/blog\/blog_prohoster\/pervyj-stabilnyj-vypusk-fedora-coreos"},"modified":"2020-02-18T14:03:25","modified_gmt":"2020-02-18T11:03:25","slug":"pervyj-stabilnyj-vypusk-fedora-coreos","status":"publish","type":"post","link":"https:\/\/prohoster.info\/en\/blog\/news\/pervyj-stabilnyj-vypusk-fedora-coreos","title":{"rendered":"The first stable release of Fedora CoreOS","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"

Fedora project developers announced<\/a><\/noindex> on stabilizing the distribution Fedora CoreOS<\/a><\/noindex> and its readiness for widespread use. Fedora CoreOS is promoted as a unified solution for running environments based on isolated containers, replacing Fedora Atomic Host and CoreOS Container Linux products. Support for CoreOS Container Linux will cease in 6 months, and Fedora Atomic Host support is expected to end in late November.<\/p>\n

Fedora CoreOS is designed to provide a minimal environment that is atomically updated automatically without administrator intervention, and standardized for mass deployment of server systems intended exclusively for running containers. The distribution provides only the minimal set of components necessary for running isolated containers \u2014 the Linux kernel, the system manager systemd, and a suite of auxiliary services for SSH access, configuration management, and update installation. <\/p>\n

The system partition is mounted in read-only mode and is not changed during operation. Configuration<\/a><\/noindex> is transmitted at boot time using the Ignition<\/a><\/noindex> (an alternative to Cloud-Init). Once the system is up and running, changing the configuration and contents of the \/etc directory is impossible; only modifying the settings profile and using it to replace the environment is allowed. In general, working with the system resembles working with container images, which are not updated in place but are rebuilt from scratch and relaunched.<\/p>\n

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. <\/p>\n

From the CoreOS Container Linux distribution, which transitioned<\/a><\/noindex> came into the hands of Red Hat after acquiring CoreOS, the Fedora CoreOS project borrowed the initial boot configuration tool (Ignition), the atomic update mechanism, and the overall product philosophy. The package management technology, support for OCI (Open Container Initiative) specifications, and additional container isolation mechanisms based on SELinux have been carried over from Atomic Host. In the future, integration with Kubernetes is planned for container orchestration on Fedora CoreOS (including on the basis of OKD<\/a><\/noindex>). <\/p>\n

The first stable release of Fedora CoreOS is built from repositories Fedora 31<\/a><\/noindex> using the rpm-ostree package.
\nThe package includes the Linux kernel 5.4, system manager systemd 243, and Ignition toolkit 2.1. Runtime support for containers is provided by Moby 18.09 (Docker) and podman 1.7. By default, cgroups v1 support is enabled for compatibility, but cgroups v2 can also be activated optionally. The ability has been implemented to install<\/a><\/noindex> on various platforms, including standard servers, QEMU, OpenStack, VMware, AWS, Alibaba, Azure, and GCP. The provided iso image can operate in live mode with booting into RAM. Network booting via PXE (netboot) is supported.<\/p>\n

Three independent branches of Fedora CoreOS are offered, for which updates addressing vulnerabilities and serious bugs are created: <\/p>\n