Bug 1956971 - "image does not match the provided context" on 32-bit arm when building a container
Summary: "image does not match the provided context" on 32-bit arm when building a con...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: podman
Version: 34
Hardware: armhfp
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Lokesh Mandvekar
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-05-04 19:07 UTC by Paul Whalen
Modified: 2021-08-06 21:52 UTC (History)
12 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-08-06 21:52:40 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
debug log (50.39 KB, text/plain)
2021-05-04 19:10 UTC, Paul Whalen
no flags Details

Description Paul Whalen 2021-05-04 19:07:49 UTC
Description of problem:

Attempting to build a container from file fails on 32-bit arm:

podman build -t fedora-httpd $(pwd)
STEP 1: FROM registry.fedoraproject.org/fedora:latest
Getting image source signatures
Copying blob bf82a539f89a done  
Copying config 8f324a4e16 done  
Writing manifest to image destination
Storing signatures
STEP 2: RUN /usr/bin/dnf install -y httpd
Fedora 34 openh264 (From Cisco) - armhfp        3.0 kB/s | 2.5 kB     00:00    
Fedora Modular 34 - armhfp                      1.3 MB/s | 3.7 MB     00:02    
Fedora Modular 34 - armhfp - Updates            276 kB/s | 724 kB     00:02    
Fedora 34 - armhfp - Updates                    2.4 MB/s | 6.7 MB     00:02    
Fedora 34 - armhfp                              2.8 MB/s |  53 MB     00:18    
..
  systemd-pam-248-2.fc34.armv7hl                                                
  systemd-rpm-macros-248-2.fc34.noarch                                          
  xkeyboard-config-2.32-2.fc34.noarch                                           

Complete!
--> da34cd8a148
? Please select an image: 
  ▸ registry.fedoraproject.org/da34cd8a148a3ad67743be86d86343a15d2ea6f9acd9981373c023fab5d24e11:latest
    registry.access.redhat.com/da34cd8a148a3ad67743be86d86343a15d2ea6f9acd9981373c023fab5d24e11:latest
    docker.io/library/da34cd8a148a3ad67743be86d86343a15d2ea6f9acd9981373c023fab5d24e11:latest
    quay.io/da34cd8a148a3ad67743be86d86343a15d2ea6f9acd9981373c023fab5d24e11:latest


Version-Release number of selected component (if applicable):
podman-3.1.2-1.fc34.armv7hl
buildah-1.20.1-4.fc34.armv7hl
crun-0.19.1-2.fc34.armv7hl


How reproducible:

Always, only on 32-bit arm. Working on AArch64 and x86_64 with the same file. 

Steps to Reproduce:
1. Attempt to create a container from file 

cat << EOF >> Containerfile
FROM registry.fedoraproject.org/fedora:latest
RUN /usr/bin/dnf install -y httpd
EXPOSE 80
CMD ["-D", "FOREGROUND"]
ENTRYPOINT ["/usr/sbin/httpd"]
EOF

2. Fails as above


Additional info:

With debug logging:

DEBU[0265] set names of image "150761619aa4af7ef36598c88a7bd5d8d1eb08deefca7f3c64cd0e87db09c2a7" to [docker.io/library/fd68fc531c4bb86fd366a1ad1d5daf909c47f39f4fe8cd4b956f7830c135d441-tmp:latest] 
DEBU[0265] saved image metadata "{\"signatures-sizes\":{\"sha256:c02394d8183860bbb38b0a8249a249c747c897b6ef1379dca925c921f7354b3f\":[]}}" 
DEBU[0266] reassigned names [] to image "150761619aa4af7ef36598c88a7bd5d8d1eb08deefca7f3c64cd0e87db09c2a7" 
DEBU[0266] parsed reference into "[overlay@/home/pwhalen/.local/share/containers/storage+/tmp/podman-run-1000/containers:overlay.mount_program=/usr/bin/fuse-overlayfs]@150761619aa4af7ef36598c88a7bd5d8d1eb08deefca7f3c64cd0e87db09c2a7" 
--> 150761619aa
DEBU[0266] parsed reference into "[overlay@/home/pwhalen/.local/share/containers/storage+/tmp/podman-run-1000/containers:overlay.mount_program=/usr/bin/fuse-overlayfs]@150761619aa4af7ef36598c88a7bd5d8d1eb08deefca7f3c64cd0e87db09c2a7" 
DEBU[0266] exporting opaque data as blob "sha256:150761619aa4af7ef36598c88a7bd5d8d1eb08deefca7f3c64cd0e87db09c2a7" 
DEBU[0266] Found local image 150761619aa4af7ef36598c88a7bd5d8d1eb08deefca7f3c64cd0e87db09c2a7 but it does not match the provided context 
? Please select an image: 
  ▸ registry.fedoraproject.org/150761619aa4af7ef36598c88a7bd5d8d1eb08deefca7f3c64cd0e87db09c2a7:latest
    registry.access.redhat.com/150761619aa4af7ef36598c88a7bd5d8d1eb08deefca7f3c64cd0e87db09c2a7:latest
    docker.io/library/150761619aa4af7ef36598c88a7bd5d8d1eb08deefca7f3c64cd0e87db09c2a7:latest
    quay.io/150761619aa4af7ef36598c88a7bd5d8d1eb08deefca7f3c64cd0e87db09c2a7:latest

Comment 1 Paul Whalen 2021-05-04 19:10:34 UTC
Created attachment 1779481 [details]
debug log

Comment 2 Lokesh Mandvekar 2021-08-05 18:19:39 UTC
Paul, can you check if this issue still occurs with v3.2.3 in updates-stable or with v3.3.0-rc1 soon to land in f34 updates-testing?

Comment 3 Paul Whalen 2021-08-06 21:52:40 UTC
(In reply to Lokesh Mandvekar from comment #2)
> Paul, can you check if this issue still occurs with v3.2.3 in updates-stable
> or with v3.3.0-rc1 soon to land in f34 updates-testing?

Working in podman-3.2.3-2.fc34.armv7hl, and podman-3.3.0-0.26.rc1.fc35.armv7hl. Thanks, closing.


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