RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Description of problem:

Podman segfaults when a Dockerfile specifies an image by its digest. For example, if a Dockerfile has `FROM centos@sha256:fe8d824220415eed5477b63addf40fb06c3b049404242b31982106ac204f6700` line, it will fail with `panic: runtime error: invalid memory address or nil pointer dereference`.

If I manually install podman-1.7.0-3.fc30.x86_64, the issue is resolved.


Version-Release number of selected component (if applicable):

podman-1.6.4-2.module_el8.1.0+272+3e64ee36.x86_64

How reproducible:

Every time

Steps to Reproduce:

I setup a repo with reproducer Dockerfiles and instructions on how to reproduce the issue:
https://github.com/mprahl/podman-reproducer

I remember this being fixed in later versions of Buildah/Podman.  Will have to talk to Matt about best ways to backport.

Created attachment 1702831 [details]
Proposed patch for 8.2.0 by Valentin Rothberg

Test with podman-2.0.4-2.module+el8.3.0+7640+fae4eedb.x86_64 and it works as expect. So set this to verified. Details:
# podman build -t test .
STEP 1: FROM centos@sha256:fe8d824220415eed5477b63addf40fb06c3b049404242b31982106ac204f6700
Getting image source signatures
Copying blob 8a29a15cefae done  
Copying config 470671670c done  
Writing manifest to image destination
Storing signatures
STEP 2: RUN ls
bin  dev  etc  home  lib  lib64  lost+found  media  mnt  opt  proc  root  run  sbin  srv  sys  tmp  usr  var
STEP 3: COMMIT test
--> c29b44a6399
c29b44a6399de4db632298d3a7b0edc7542982536f83937ec7eba8f4133ca635

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (Moderate: container-tools:rhel8 security, bug fix, and enhancement update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2020:4694