Skip to content
This repository has been archived by the owner on May 24, 2024. It is now read-only.

README.md: Misc updates #491

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
44 changes: 42 additions & 2 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -8,6 +8,8 @@ The longer term vision of this project is that the build infrastructure
upstream operating systems. For now, this project acts as a more central
point for this across these distributions.

Current WIP documentation: <https://gitlab.com/bootc-org/fedora-bootc/docs>
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Shouldn't this link to the rendered docs instead?


## Motivation

The original Docker container model of using "layers" to model
Expand All @@ -16,9 +18,47 @@ aims to apply the same technique for bootable host systems - using
standard OCI/Docker containers as a transport and delivery format
for base operating system updates.

## More information
## Generated container images

At the moment the main image is `quay.io/centos-bootc/centos-bootc:stream9`
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Minor/optional: missing period.


## Building
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

OK, I hadn't paid attention to this PR until now but this section is similar to what I propose on the Fedora side in https://gitlab.com/fedora/bootc/base-images/-/merge_requests/6. I think (as done there) it'd be good to link to the relevant docs pages and mention that layering is the expected flow. WDYT about taking what I have there here, and moving the Mac bit into the docs so that the README stays shorter?


The build process is 95% just installing RPM content into a container
image; there is some non-RPM config files etc. in this repository
too.

See:

- [Containerfile.centos-stream9]
- [Containerfile.centos-stream10]
- [Containerfile.fedora-40]
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should remove this one now.


For example:

```bash
podman build --security-opt=label=disable --cap-add=all --device /dev/fuse \
-f Containerfile.centos-stream9 -t localhost/centos-bootc:stream9
```

NOTE: This will not work when using "podman machine" over the remote client
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What is blowing up on a MAC?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Well I didn't dig deep into debugging it honestly. On Linux at least I get a really weird error

error: Installing packages: Updating rpm-md repo 'baseos': metadata[process] already locked by /proc/self/exe(17)

I haven't even tried to debug but I suspect the problem has something to do with 9p (which has more bugs than virtiofs)...we need to convert podman-machine on Linux to use libvirt probably.

(e.g. the default on MacOS/Windows).
In order to do a build on MacOS/Windows, first:

`podman machine ssh`

Then, navigate to your source code directory:

`cd /path/to/source/code` (e.g. `/Users/chloe/src/centos-bootc`

And finally, invoke the same

`podman build ...`

per above.

See: <https://bootc-org.gitlab.io/documentation/>
There is also <https://gitlab.com/bootc-org/fedora-bootc/base-images-experimental>
for a new even more container-native build system.

## Badges

Expand Down
Loading