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 requirement on exact matching host architecture #682

Closed
cgwalters opened this issue Jul 15, 2024 · 3 comments
Closed

Add requirement on exact matching host architecture #682

cgwalters opened this issue Jul 15, 2024 · 3 comments
Labels
bug Something isn't working enhancement New feature or request

Comments

@cgwalters
Copy link
Collaborator

Today for the case of an image without a manifest list e.g. podman pull will just warn if the target image architecture doesn't match. One reason for this is that one may have qemu userspace emulation enabled.

For bootc, we are never going to support "booting" with qemu emulation, doesn't make any sense. We should change the fetch logic to hard require an architecture match (probably in ostree-rs-ext, but we could add a check here too).

@cgwalters cgwalters added bug Something isn't working enhancement New feature or request labels Jul 15, 2024
@cgwalters
Copy link
Collaborator Author

cgwalters commented Jul 15, 2024

This also relates to #640 in that if we started spawning the new root as a container we could in theory get some of this for free...but we'd actually want to somehow explicitly turn off the binfmt_misc when targeting the new root, which seems messy.

@cgwalters
Copy link
Collaborator Author

PR in ostreedev/ostree-rs-ext#656

@cgwalters
Copy link
Collaborator Author

This one is done as we've now rolled in that fix from ostree-rs-ext.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant