Bug 1997789 - no image found in manifest list for architecture arm, variant "v7", OS linux
Summary: no image found in manifest list for architecture arm, variant "v7", OS linux
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora Container Images
Classification: Fedora
Component: fedora-container-image
Version: 36
Hardware: armv7l
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: Clement Verna
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: ARMTracker
TreeView+ depends on / blocked
 
Reported: 2021-08-25 19:27 UTC by Paul Whalen
Modified: 2023-05-25 19:32 UTC (History)
15 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2023-05-25 19:32:45 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Paul Whalen 2021-08-25 19:27:21 UTC
Description of problem:

Trying to pull the latest Fedora image from the registry fails on 32-bit arm:

[root@rpi2-1 ~]# podman pull registry.fedoraproject.org/fedora:latest

Trying to pull registry.fedoraproject.org/fedora:latest...
Error: choosing an image from manifest list docker://registry.fedoraproject.org/fedora:latest: no image found in manifest list for architecture arm, variant "v7", OS linux



Version-Release number of selected component (if applicable):
podman-3.3.0-1.fc35.armv7hl

How reproducible:
Every time. 

Actual results:
podman --log-level=debug pull registry.fedoraproject.org/fedora:latest
INFO[0000] podman filtering at log level debug          
DEBU[0000] Called pull.PersistentPreRunE(podman --log-level=debug pull registry.fedoraproject.org/fedora:latest) 
DEBU[0000] Merged system config "/usr/share/containers/containers.conf" 
DEBU[0000] Using conmon: "/usr/bin/conmon"              
DEBU[0000] Initializing boltdb state at /var/lib/containers/storage/libpod/bolt_state.db 
DEBU[0000] Using graph driver overlay                   
DEBU[0000] Using graph root /var/lib/containers/storage 
DEBU[0000] Using run root /run/containers/storage       
DEBU[0000] Using static dir /var/lib/containers/storage/libpod 
DEBU[0000] Using tmp dir /run/libpod                    
DEBU[0000] Using volume path /var/lib/containers/storage/volumes 
DEBU[0000] Set libpod namespace to ""                   
DEBU[0000] [graphdriver] trying provided driver "overlay" 
DEBU[0000] cached value indicated that overlay is supported 
DEBU[0000] cached value indicated that metacopy is being used 
DEBU[0000] cached value indicated that native-diff is not being used 
INFO[0000] Not using native diff for overlay, this may cause degraded performance for building images: kernel has CONFIG_OVERLAY_FS_REDIRECT_DIR enabled 
DEBU[0000] backingFs=extfs, projectQuotaSupported=false, useNativeDiff=false, usingMetacopy=true 
DEBU[0000] Initializing event backend journald          
DEBU[0000] configured OCI runtime runc initialization failed: no valid executable found for OCI runtime runc: invalid argument 
DEBU[0000] configured OCI runtime kata initialization failed: no valid executable found for OCI runtime kata: invalid argument 
DEBU[0000] configured OCI runtime runsc initialization failed: no valid executable found for OCI runtime runsc: invalid argument 
DEBU[0000] Using OCI runtime "/usr/bin/crun"            
INFO[0000] Found CNI network podman (type=bridge) at /etc/cni/net.d/87-podman.conflist 
DEBU[0000] Default CNI network name podman is unchangeable 
INFO[0000] Setting parallel job count to 13             
DEBU[0000] Pulling image registry.fedoraproject.org/fedora:latest (policy: always) 
DEBU[0000] Looking up image "registry.fedoraproject.org/fedora:latest" in local containers storage 
DEBU[0000] Trying "registry.fedoraproject.org/fedora:latest" ... 
DEBU[0000] Trying "registry.fedoraproject.org/fedora:latest" ... 
DEBU[0000] Trying "registry.fedoraproject.org/fedora:latest" ... 
DEBU[0000] Loading registries configuration "/etc/containers/registries.conf" 
DEBU[0000] Loading registries configuration "/etc/containers/registries.conf.d/000-shortnames.conf" 
DEBU[0000] Attempting to pull candidate registry.fedoraproject.org/fedora:latest for registry.fedoraproject.org/fedora:latest 
DEBU[0000] parsed reference into "[overlay@/var/lib/containers/storage+/run/containers/storage:overlay.mountopt=nodev,metacopy=on]registry.fedoraproject.org/fedora:latest" 
Trying to pull registry.fedoraproject.org/fedora:latest...
DEBU[0000] Copying source image //registry.fedoraproject.org/fedora:latest to destination image [overlay@/var/lib/containers/storage+/run/containers/storage:overlay.mountopt=nodev,metacopy=on]registry.fedoraproject.org/fedora:latest 
DEBU[0000] Trying to access "registry.fedoraproject.org/fedora:latest" 
DEBU[0000] No credentials for registry.fedoraproject.org found 
DEBU[0000] Using registries.d directory /etc/containers/registries.d for sigstore configuration 
DEBU[0000]  Using "default-docker" configuration        
DEBU[0000]  No signature storage configuration found for registry.fedoraproject.org/fedora:latest, using built-in default file:///var/lib/containers/sigstore 
DEBU[0000] Looking for TLS certificates and private keys in /etc/docker/certs.d/registry.fedoraproject.org 
DEBU[0000] GET https://registry.fedoraproject.org/v2/   
DEBU[0001] Ping https://registry.fedoraproject.org/v2/ status 200 
DEBU[0001] GET https://registry.fedoraproject.org/v2/fedora/manifests/latest 
DEBU[0001] Content-Type from manifest GET is "application/vnd.docker.distribution.manifest.list.v2+json" 
DEBU[0001] Using blob info cache at /var/lib/containers/cache/blob-info-cache-v1.boltdb 
DEBU[0001] Error pulling candidate registry.fedoraproject.org/fedora:latest: choosing an image from manifest list docker://registry.fedoraproject.org/fedora:latest: no image found in manifest list for architecture arm, variant "v7", OS linux 
Error: choosing an image from manifest list docker://registry.fedoraproject.org/fedora:latest: no image found in manifest list for architecture arm, variant "v7", OS linux

Comment 1 Matthew Heon 2021-08-25 20:31:28 UTC
The manifest list does have an entry for 32-bit arm:

mheon@Marlborough code/podman (main)$ podman manifest inspect fedora:latest
...
        {
            "mediaType": "application/vnd.docker.distribution.manifest.v2+json",
            "size": 429,
            "digest": "sha256:4dd27dd95a83817a5e9c305fdf639948838c08f2c1dff0622e720da2aaffc2a5",
            "platform": {
                "architecture": "armhfp",
                "os": "linux"
            }
        },
...


First thought is that it's architecture is set to "armhfp" instead of "arm" - that strikes me as potentially incorrect. I'll add Valentin to CC, as he's been dealing with quite a lot recently because of the image rework.

Comment 2 Paul Whalen 2021-08-25 23:05:20 UTC
Adding '--arch armhfp' works

podman pull registry.fedoraproject.org/fedora:latest --arch armhfp
Trying to pull registry.fedoraproject.org/fedora:latest...
Getting image source signatures
Copying blob 101fd87d5ca1 done  
Copying config 856b5adac2 done  
Writing manifest to image destination
Storing signatures
856b5adac2a7f327f8d3147c4b407b151e14e863b9a6c6c526c904766aceefa3

Comment 3 Valentin Rothberg 2021-08-26 09:45:33 UTC
`armhfp` is not a "valid" value.  The image-spec states that the architecture should only mention values of GOARCH [1].  For Linux, there's only "arm" and "arm64". The variant field should be used to further discriminate the various arm platforms.  I suggest Fedora corrects the manifest list.

[1] https://golang.org/doc/install/source#environment

Comment 6 Clement Verna 2021-08-27 09:19:16 UTC
This was introduced by https://pagure.io/releng/pull-request/10249.  I ll work on fix

Comment 7 Clement Verna 2021-08-27 10:29:53 UTC
I think this should fix it https://github.com/redhat-imaging/imagefactory/pull/449/files

Comment 8 Paul Whalen 2022-04-07 17:34:42 UTC
The workaround of using '--arch armhfp' now fails. Looking at the manifest- armhfp, armv7hl or any variant of it no longer exists.

Comment 9 Ben Cotton 2023-04-25 18:26:14 UTC
This message is a reminder that Fedora Linux 36 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora Linux 36 on 2023-05-16.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
'version' of '36'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, change the 'version' 
to a later Fedora Linux version. Note that the version field may be hidden.
Click the "Show advanced fields" button if you do not see it.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora Linux 36 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora Linux, you are encouraged to change the 'version' to a later version
prior to this bug being closed.

Comment 10 Ludek Smid 2023-05-25 19:32:45 UTC
Fedora Linux 36 entered end-of-life (EOL) status on 2023-05-16.

Fedora Linux 36 is no longer maintained, which means that it
will not receive any further security or bug fix updates. As a result we
are closing this bug.

If you can reproduce this bug against a currently maintained version of Fedora Linux
please feel free to reopen this bug against that version. Note that the version
field may be hidden. Click the "Show advanced fields" button if you do not see
the version field.

If you are unable to reopen this bug, please file a new report against an
active release.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.