container

Fedora CoreOS (FCOS), and the used configuration system Ignition, does currently not support injecting the needed configuration file via so called config-drives. It is required to host this file on a separate web server or to use a custom data injection mechanism of one of the supported cloud providers (like user-data from Amazon AWS EC2). As this can be difficult for users with simpler use cases and with no access to external web servers, I want to provide a short overview how to embed the configuration file into the FCOS image itself.

Fedora CoreOS, the new operation system developed by the Fedora community and Red Hat, finally left the preview phase. As a user of the now deprecated Atomic Hosts (available for Fedora, CentOS, Red Hat Enterprise Linux) a good opportunity to try it out and give some hints how to configure your first working system.

When dealing with modern IT infrastructure the chances are pretty high that you already came in contact with virtualized systems. Be it running a virtual machine on your Linux or Windows computer with software like VirtualBox, using virtualized networks like VPN or working with modern container-based virtualization as provided by tooling such as Docker.

The broad term virtualization can cover a lot of ground and my main focus in this article lies on platform as well as container-based virtualization; with the goal to provide a basic distinction between different virtualization techniques while introducing some key concepts to build upon.