podman manifest add
disregarding architecture
#24016
Labels
kind/bug
Categorizes issue or PR as related to a bug.
podman manifest add
disregarding architecture
#24016
Issue Description
When trying to build a multi-arch OCI manifest with Podman, I am receiving a strange error where it appears Podman is looking for the incorrect image architecture.
As you can see, I am explicitly telling Podman I wish to use an arm64 image in this build, however it still incorrectly looks to the registry to add an amd64 image.
Using a digest rather than the image tag, the command exits successfully and the image is added to the manifest.
For detailed reproduction steps, please see below.
Steps to reproduce the issue
Steps to reproduce the issue
podman manifest create test
# successfulpodman manifest add test ghcr.io/rsturla/akmods/multiarch-nvidia:40-x86_64
# successfulpodman manifest add test ghcr.io/rsturla/akmods/multiarch-nvidia:40-arm64
# errorDIGEST=$(skopeo inspect --raw docker://ghcr.io/rsturla/akmods/multiarch-nvidia:40-arm64 | jq -r '.manifests[] | select(.platform.architecture == "arm64") | .digest')
# successfulpodman manifest add test ghcr.io/rsturla/akmods/multiarch-nvidia@$DIGEST
# successfulDescribe the results you received
Rather than Podman adding the correct ARM64 image, it looks to the registry for an AMD64 image, and fails when it cannot be found. Even after explicitly defining the architecture.
Describe the results you expected
I expect to be able to add both AMD64 and ARM64 images to the manifest using their tags.
podman info output
Podman in a container
No
Privileged Or Rootless
Rootless
Upstream Latest Release
Yes
Additional environment details
Additional environment details
Additional information
The issue appears similar to this - both are using scratch images and displaying the same error, however the issue linked was resolved through a patch.
The text was updated successfully, but these errors were encountered: