public
/
bootc-base-images
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

README.md: Update for migration to gitlab

This commit is contained in:
Colin Walters 2023-09-08 16:03:14 -04:00
parent d055946bdf
commit 0360147e15
1 changed files with 14 additions and 11 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

25
README.md
View File

@ -1,6 +1,10 @@
# Demonstration base images for use with bootc
# Demonstration bootable container base images
This repository contains "base images" suitable for use with [bootc](https://github.com/containers/bootc).
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
@ -8,22 +12,21 @@ via `rpm-ostree compose image`.
## Available images
### Fedora
### Fedora 38
[registry.gitlab.com/cgwalters-playground/bootc-demo-base-images/fedora-boot:latest](https://gitlab.com/cgwalters-playground/bootc-demo-base-images/container_registry/4567470)
[ghcr.io/cgwalters/fedora-oscore](https://github.com/cgwalters/bootc-demo-base-images/pkgs/container/fedora-oscore)
### CentOS Stream 9
[ghcr.io/cgwalters/c9s-oscore](https://github.com/cgwalters/bootc-demo-base-images/pkgs/container/c9s-oscore)
[registry.gitlab.com/cgwalters-playground/bootc-demo-base-images/c9s-boot](https://gitlab.com/cgwalters-playground/bootc-demo-base-images/container_registry/4567470)
## What's in them?
The [current manifest definitions](oscore/) were forked from Fedora CoreOS, then some things were
removed such as `moby-engine` and `ignition` and `clevis`.
The [current manifest definitions](oscore/) were forked from Fedora CoreOS, but significantly
cut down.
Then, `bootc` is a key addition.
The content set is obviously subject to change and debate.
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.
@ -32,7 +35,7 @@ Ideally, we support a workflow where even `rpm-ostree` can be removed after buil
Here's an example command:
```
$ sudo rpm-ostree compose image --authfile ~/.config/containers/myquay.json --cachedir=cache -i --format=registry fedora.yaml quay.io/cgwalters/fedora-oscore
$ 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/