-
Notifications
You must be signed in to change notification settings - Fork 26
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
Base Image Build problem mongodb and centos Stream 9 with podman on a non-Intel / Apple Silicon M1 / M2 / M3 Mac #56
Comments
Solved the issue building with podman on a non-Intel / Apple Silicon M1 / M2 / M3 Mac with hints from here: https://docs.podman.io/en/latest/markdown/podman-build.1.html Quoting: When building an image with Podman, you can specify the --arch flag to select the desired CPU architecture for the image. By default, Podman uses the CPU architecture of the machine it is running on. This allows you to build multi-architecture images using Podman, which can be useful for running the same application across different CPU architectures. Solution: explicitely set https://github.com/opendatahub-io-contrib/workbench-images/blob/main/base/Makefile#L26 https://github.com/opendatahub-io-contrib/workbench-images/blob/main/base/Makefile#L33 Also applies to podman run in the Makefile inspect section: https://github.com/opendatahub-io-contrib/workbench-images/blob/main/base/Makefile#L57 On previous Intel Mac with homebrew installed Podman, this issue never happened. Result: Successful resolve of the architecture, in this case amd64, with the help of yum inside the build container.
|
$ pwd
/workbench-images/base
$ make all RELEASE=2024c DATE=20240808
Podman Terminal output, running this on Mac OS X ... should not matter though because yum runs inside centos stream 9,
quay.io/sclorg/python-311-c9s:c9s
correct?The text was updated successfully, but these errors were encountered: