-
Notifications
You must be signed in to change notification settings - Fork 18
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
KNOWN ISSUE: Unable to cross-arch build #808
Comments
See osbuild/bootc-image-builder#619 intention is to add documentation for |
UPDATE there's a solution now! With Rosetta disabled and the instructions from osbuild/bootc-image-builder#619 (comment) I am now able to build. |
### What does this PR do? * Adds documentation regarding cross-arch building * Docs are meant as an intermediary until podman machine is patched with the new QEMU calls * When QEMU is patched, the only thing needed is to "disable rosetta" ### Screenshot / video of UI <!-- If this PR is changing UI, please include screenshots or screencasts showing the difference --> N/A ### What issues does this PR fix or reference? <!-- Include any related issues from Podman Desktop repository (or from another issue tracker). --> References podman-desktop#808 ### How to test this PR? <!-- Please explain steps to reproduce --> Follow documentation instructions on how to cross-arch build again. Signed-off-by: Charlie Drage <[email protected]>
### What does this PR do? * Adds documentation regarding cross-arch building * Docs are meant as an intermediary until podman machine is patched with the new QEMU calls * When QEMU is patched, the only thing needed is to "disable rosetta" ### Screenshot / video of UI <!-- If this PR is changing UI, please include screenshots or screencasts showing the difference --> N/A ### What issues does this PR fix or reference? <!-- Include any related issues from Podman Desktop repository (or from another issue tracker). --> References podman-desktop#808 ### How to test this PR? <!-- Please explain steps to reproduce --> Follow documentation instructions on how to cross-arch build again. Signed-off-by: Charlie Drage <[email protected]>
### What does this PR do? * Adds documentation regarding cross-arch building * Docs are meant as an intermediary until podman machine is patched with the new QEMU calls * When QEMU is patched, the only thing needed is to "disable rosetta" ### Screenshot / video of UI <!-- If this PR is changing UI, please include screenshots or screencasts showing the difference --> N/A ### What issues does this PR fix or reference? <!-- Include any related issues from Podman Desktop repository (or from another issue tracker). --> References podman-desktop#808 ### How to test this PR? <!-- Please explain steps to reproduce --> Follow documentation instructions on how to cross-arch build again. Signed-off-by: Charlie Drage <[email protected]>
### What does this PR do? * Adds documentation regarding cross-arch building * Docs are meant as an intermediary until podman machine is patched with the new QEMU calls * When QEMU is patched, the only thing needed is to "disable rosetta" ### Screenshot / video of UI <!-- If this PR is changing UI, please include screenshots or screencasts showing the difference --> N/A ### What issues does this PR fix or reference? <!-- Include any related issues from Podman Desktop repository (or from another issue tracker). --> References #808 ### How to test this PR? <!-- Please explain steps to reproduce --> Follow documentation instructions on how to cross-arch build again. Signed-off-by: Charlie Drage <[email protected]>
Marked this as Done as part of sprint planning as we now have the document on the README: https://github.com/containers/podman-desktop-extension-bootc?tab=readme-ov-file#known-issues But I will leave this open in case someone else stumbles upon this issue. |
Bug description
If you have output issues such as:
There are current issues upstream regarding building the default stream9 image or cross-arch builds that you may encounter:
Operating system
all OS'
Version
next (development version)
Steps to reproduce
No response
Relevant log output
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: