-
Notifications
You must be signed in to change notification settings - Fork 62
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
Deprecate --local
flag (HMS-3792)
#423
base: main
Are you sure you want to change the base?
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Overall LGTM just two nits
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for this! Looks good, one tiny idea/suggestion inline.
Arghhh of course this breaks |
996a9ff
to
0f0f46f
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The joy and simplicity of a mostly-red PR :)
0f0f46f
to
53956d3
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you!
53956d3
to
4356c1e
Compare
|
4356c1e
to
bc9b951
Compare
bc9b951
to
cb769a3
Compare
Okay it's finally green now. Removing the flag also broke the cross-arch integration tests :/ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
One more note/question but could be followup (just defensive)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I love this! :)
Marking this as request changes, because I want to first talk to the podman desktop folks if this is alright for them, and I want to figure out if we can somehow have bib releases, so users know what version they run, and thus which flags are supported and what's the default behaviour (git SHAs aren't very friendly in this case unfortunately).
acc9c79
to
e3d37c7
Compare
Thanks! 👍 |
Merge conflicts in the queue |
b159ca1
be11011
to
b159ca1
Compare
6a95c3e
to
22f4e9c
Compare
Hi! So I'm currently using bootc-image-builder and am purposely not using --local, and being forced to use --local would break the tool for me. More specifically, on my build computer I set the If you remove the local option, would you be willing to also find the places where the graphroot is assumed to be EDIT: Thanks for this great tool and bootc in general, it really is a great way to build the custom images I want for my application, while still being able to take advantage of all the benefits of a full Linux Distro. |
@jpace121 I think your use case can be solved by mounting both into the bootc-image-builder container.
Can you see if that works? The
If the path that graphroot points to isn't mounted in the container, there's not much we can do from inside the container itself to reach it automatically. Unless I'm misunderstanding the suggestion. |
This PR is stale because it has been open 30 days with no activity. Remove "Stale" label or comment or this will be closed in 7 days. |
This PR was closed because it has been stalled for 30+7 days with no activity. |
22f4e9c
to
cb3dcca
Compare
Pulling container images before building would break in the case of authenticated images on podman machine, since the auth file lives on the host and not podman machine and won't know about it. This commit deprecates the `--local` flag and warns users when it is passed to the CLI so that this won't break things for anyone who might already be using the flag. This change means that the user will have to ensure that the container is pulled to the local container store before initiating the build. Co-authored-by: Ondřej Budai <[email protected]>
Ensure that the containers have been copied into local storage for all test cases. We need to explicitly pull the container into local containers storage with the correct arch otherwise cross-arch building fails. The helper function uses the host-arch as a fallback when no target arch is provided.
Since all containers are coming from local storage and require the user to pull in the container before-hand, we can disable the `--tls-verify` flag. The containers will not be resolved from a remote registry but rather from the local container store.
cb3dcca
to
9c6b865
Compare
Pulling container images before building would break in the case of authenticated images on podman machine, since the auth file lives on the host and podman machine and won't know about it.
This commit deprecates the
--local
flag and puts the requirement on the user to ensure that the container is in local storage before initiating the build.