-
Notifications
You must be signed in to change notification settings - Fork 92
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
Bootc switch issues #1024
Comments
Once you've done the switch, you can use |
|
Maybe I have a funny workflow, but I kinda like it, I just rebuild a locally maintained Containerfile when I want to update or add more software, means I can use dnf or any other install technique I want (within reason) |
Once you have done a |
Ah ok interesting, I'll try that |
Are you overriding the bootc binary in the container build somehow? What host version is this? Is it specific to having |
It's this Containerfile specifically:
chcon fails without doing bootc usr-overlay first |
Can you paste the output of |
I'm off now but I'll do it Monday, just for the record this is an rpm-ostree Kinoite system converted to bootc via "bootc switch". That's the easiest way to install a Silverblue/Kinoite bare metal machine that I know of, start with an rpm-ostree .iso . |
At the bottom is a wrapper script I use to do podman build and bootc switch. Bug 1 is known I think, we have to do chcon to solve an selinux issue. Bug 2 is if you try and bootc switch to a container with the same name as the current one, it does nothing (even though one may have made an edit to the container image since, etc.). I workaround this by getting the sha from
podman images -q
, but it should be able to recognise it's not the same image as currently booted.The text was updated successfully, but these errors were encountered: