Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add suggestion for LABEL containers.bootc 1 #299

Merged
merged 1 commit into from
Feb 5, 2024

Conversation

cgwalters
Copy link
Collaborator

As we aim to slowly move away from ostree, let's add a bootc label that we expect to be used. For now, this is just a warning.

I will change rpm-ostree to add this by default if we take this.

But this one is also an important step for if we ever add the flow of simply deriving from an existing application base image.

@github-actions github-actions bot added the documentation Improvements or additions to documentation label Feb 2, 2024
@cgwalters cgwalters added the area/updates Related to upgrading between versions label Feb 2, 2024
Copy link
Member

@jmarrero jmarrero left a comment

Choose a reason for hiding this comment

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

lgtm

Copy link
Member

@vrothberg vrothberg left a comment

Choose a reason for hiding this comment

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

LGTM

cgwalters added a commit to cgwalters/centos-bootc that referenced this pull request Feb 5, 2024
Pairs with containers/bootc#299

This is intended to be the new canonical label for bootc-compatible
images, as opposed to the existing `ostree.linux` etc.
As we aim to slowly move away from ostree, let's add a bootc label
that we expect to be used.  For now, this is just a warning.

I will change rpm-ostree to add this by default if we take this.

But this one is also an important step for if we ever add the
flow of simply deriving from an existing application base image.

Signed-off-by: Colin Walters <walters@verbum.org>
@cgwalters
Copy link
Collaborator Author

OK we learned from #297 that our usage of eprintln! is problematic, so I changed this to use the systemd journal.

In the general case we're probably going to need to grow a logging abstraction a bit like what rpm-ostree has where we can write to a mix of stdout (when running as a systemd unit directly e.g. as part of bootc-fetch-apply-updates.service or when running under podman w/out systemd) or to the journal (when running outside of a unit, but on a booted host, which is the current default interactive case, but cc #2 )

@cgwalters cgwalters merged commit faf478d into containers:main Feb 5, 2024
11 checks passed
cgwalters added a commit to cgwalters/ostree-rs-ext that referenced this pull request Feb 5, 2024
See containers/bootc#299

Since we want to move ostree more into the background, this new
label name puts the focus on bootc.
@cgwalters
Copy link
Collaborator Author

Also did ostreedev/ostree-rs-ext#595 related to this

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/updates Related to upgrading between versions documentation Improvements or additions to documentation
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants