For many years, we've had Linux and containers operating in connected but separate worlds. Today, we are excited to announce that we are bringing these worlds together. We're making the ecosystem of content available to you in containers, now to your core Linux systems. Containers now become the language for building the OS. Boot them to your core Linux systems. Modify them in a Containerfile/Dockerfile. Whether standalone images to modify as you see fit in your datacenter, immutable images at the edge or worker nodes in Kubernetes/OpenShift - one, consistent approach. We're always striving to make developing applications across the hybrid cloud easier and to make your IT landscape easier to manage even as you face increasing complexity. And we hope you are as excited about this as we are.
This project's toplevel goal is to create "base" bootable container images from Fedora ELN and CentOS Stream packages.
See install.md.
This is an in-development project not intended for production use yet.
Fedora CoreOS today is not small; there are multiple reasons for this, but primarily because it was created in a pre-bootable-container time. Not everyone wants e.g. moby-engine.
But going beyond size, the images produced by this project will focus on a container-native flow. We will ship a (container) image that does not include Ignition for example.
We sometimes say that RHEL CoreOS has FCOS as an upstream but this is only kind of true; RHEL CoreOS includes a subset of FCOS content, and is lifecycled with OCP.
An explicit goal of this project is to produce bootable container images that can be used as base images for RHEL CoreOS; for more on this, see e.g. openshift/os#799
It is an explicit goal that Sagano also becomes a "base input" to RHEL for Edge.
From Wikipedia:
Bamboo Forest, Arashiyama Bamboo Grove or Sagano Bamboo Forest, is a natural forest of bamboo in Arashiyama, Kyoto, Japan
This is part of Project Sagano.
These images are technology demonstrators, not for production use. The
intention is that these images are generated by the OS vendor or
distribution.
Or, you can fork this repository and generate your own via
rpm-ostree compose image
.
At the moment these demonstration builds use Fedora 38 and CentOS Stream 9.
This is the basic tier; it has effectively just:
- kernel systemd selinux-policy-targeted bootc
You are generally going to need to generate derived images from this; installing it on its own will boot to a system with no automatic networking support, no SSH, and no default passwords etc.
This is larger system.
- NetworkManager, chrony
- rpm-ostree (to install packages and in case it's useful "day 2")
- openssh-server
At the current time, it does not include Ignition or cloud-init; so you will still need to derive from it in order to inject a mechanism to log in in many cases. However, it will work to install it using e.g. Anaconda and set up users and passwords that way.
registry.gitlab.com/centos/cloud/sagano/fedora-boot-tier-0:38
registry.gitlab.com/centos/cloud/sagano/fedora-boot-tier-1:38
registry.gitlab.com/centos/cloud/sagano/fedora-boot-tier-0:eln
registry.gitlab.com/centos/cloud/sagano/fedora-boot-tier-1:eln
registry.gitlab.com/centos/cloud/sagano/centos-boot-tier-0:stream9
registry.gitlab.com/centos/cloud/sagano/centos-boot-tier-0-rt:stream9
(realtime kernel)registry.gitlab.com/centos/cloud/sagano/centos-boot-tier-1:stream9
registry.gitlab.com/centos/cloud/sagano/centos-boot-tier-1-rt:stream9
(realtime kernel)
These images pull from git main/master of RPMs using COPRs for selected projects.
registry.gitlab.com/centos/cloud/sagano/fedora-boot-tier-0-dev:38
registry.gitlab.com/centos/cloud/sagano/fedora-boot-tier-1-dev:38
The current manifest definitions tier-0 and tier-1 were forked from Fedora CoreOS, but significantly cut down.
The existing content set is obviously subject to change and debate.
Here's an example command:
sudo rpm-ostree compose image --authfile ~/.config/containers/myquay.json --cachedir=cache -i --format=ociarchive centos-tier-0-stream9.yaml centos-tier-0-stream9.ociarchive
In some situations, copying to a local .ociarchive
file is convenient. You
can also push to a registry with --format=registry
.
More information at https://coreos.github.io/rpm-ostree/container/
- Merge this repository into https://gitlab.com/fedora/boot-container-base (e.g.)
- Add these images to Fedora, but in the
fedoraci
namespace, like ELN. - The images are built via Pungi
- The sync container script is modified to include this
- Add this to CI tooling in Fedora
- Change fedora-coreos-config to inherit from this as a git submodule
- (?) Fork https://gitlab.com/fedora/boot-container-base into something under https://gitlab.com/CentOS/cloud/ and start building C9S versions there?
- https://gitlab.com/redhat/centos-stream
Badge | Description | Service |
---|---|---|
Dependencies | Renovate | |
Static quality gates | pre-commit |