-
Notifications
You must be signed in to change notification settings - Fork 70
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
Optionally expose all underlying container metadata in status #348
Comments
Or maybe it would be better as Maybe we should have |
|
@cgwalters what if we namespace the labels with something like |
Hmm what would be the use case for that? Adding container metadata is a build-time thing right?
The question of exposing container information in |
ack, I wrongly thought this was for rpm-ostree status, but it's bootc status, nevermind :) |
right, I was imagining that |
As someone deploying a bootc system, I may want to add custom labels (or OCI annotations) into my image, and I want to be able to see that on the client side to potentially act on it.
Today this is all squirreled away in the underlying ostree-container store, one can extract it with
ostree container metadata
, but that's awkward and we want to get away from exposing ostree (this also relates to #215 )Maybe what we do for now is something like
bootc status --full
which would dump the container manifest and config into the image status?The text was updated successfully, but these errors were encountered: