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

Consider using the "name" argument to [[containers]] instead of a system-wide image configuration. #8

Open
flozanorht opened this issue Jan 2, 2025 · 1 comment

Comments

@flozanorht
Copy link
Collaborator

From slack tread: https://redhat-internal.slack.com/archives/C022TDCV3FH/p1735819746307919
Achilleas Koutsou
[email protected]

achilleas
Today at 9:09 AM
Hi
@Fernando Lozano
. The team is slowly trickling back in from the holiday break starting today. What's the status of your issues right now?
It's not entirely clear to me what you're trying to do and what the issues are, but did you know you can specify the source of the container and the local name (ref) separately in the blueprint?
https://osbuild.org/docs/user-guide/blueprint-reference/#containers
For example,
[[containers]]
source = "localhost/fedora:41"
name = "quay.io/fedora/fedora:41"
Will pull the fedora:41 container from localhost but in the local storage in the image, it will be named quay.io/fedora/fedora:41 so it can pull/update from that ref.
Does this help? (edited)

@flozanorht
Copy link
Collaborator Author

This won't handle signature checks. Maybe it "just works" after I get from the MicroShift team the docs for mirroring images with signatures and understand how to make cosign work properly.

It has the advantage that mirroring settings are in the blueprint instead of system wide, and don't require a reboot or osbuild workers restart.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant