87dd6b3e69
|
||
|---|---|---|
| oscore | ||
| .gitlab-ci.yml | ||
| COPYING | ||
| LICENSE | ||
| README.md | ||
| c9s-base.yaml | ||
| c9s-rt.yaml | ||
| c9s.repo | ||
| c9s.yaml | ||
| fedora-next.repo | ||
| fedora-rawhide.repo | ||
| fedora.repo | ||
| fedora.yaml | ||
README.md
Demonstration bootable container base images
The intention is to introduce "bootable" base images that pair with existing "application" base images, e.g.:
- quay.io/fedora/fedora-boot:39
- quay.io/centos/centos-boot:stream9
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.
Available images
Fedora 38
registry.gitlab.com/cgwalters-playground/bootc-demo-base-images/fedora-boot:latest
CentOS Stream 9
registry.gitlab.com/cgwalters-playground/bootc-demo-base-images/c9s-boot
What's in them?
The current manifest definitions were forked from Fedora CoreOS, but significantly cut down.
The existing content set is obviously subject to change and debate.
Ideally, we support a workflow where even rpm-ostree can be removed after builds.
Building
Here's an example command:
$ sudo rpm-ostree compose image --authfile ~/.config/containers/myquay.json --cachedir=cache -i --format=oci fedora.yaml fedora.oci
More information at https://coreos.github.io/rpm-ostree/container/