Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
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 (Important: 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-2022:1762
I don't know if this is the right place to mention this, but my Dockerfile looks like:
$ cat Dockerfile
FROM registry.access.redhat.com/ubi8/ubi:latest
RUN dnf clean all
RUN dnf update; dnf upgrade
RUN dnf install -y podman
CMD ["echo hello world"]
And this is what building it looks like:
> [4/4] RUN dnf install -y podman:
#7 0.812 Updating Subscription Management repositories.
#7 0.813 Unable to read consumer identity
#7 0.818
#7 0.818 This system is not registered with an entitlement server. You can use subscription-manager to register.
#7 0.818
#7 0.868 Last metadata expiration check: 0:16:12 ago on Thu May 12 14:13:14 2022.
#7 1.112 Error:
#7 1.112 Problem: conflicting requests
#7 1.112 - nothing provides libsubid.so.3()(64bit) needed by podman-2:4.0.2-6.module+el8.6.0+14877+f643d2d6.x86_64
#7 1.113 (try to add '--skip-broken' to skip uninstallable packages or '--nobest' to use not only best candidate packages)
I'm trying to figure out why libsubid.so.3 is missing?
(In reply to Brandon Palm from comment #13)
> #7 1.112 - nothing provides libsubid.so.3()(64bit) needed by
Is this RHEL8.6?
What happens if you try to install 'shadow-utils-subid' package manually?
=> ERROR [4/4] RUN dnf install -y shadow-utils-subid podman 0.8s
------
> [4/4] RUN dnf install -y shadow-utils-subid podman:
#7 0.564 Updating Subscription Management repositories.
#7 0.564 Unable to read consumer identity
#7 0.567
#7 0.567 This system is not registered with an entitlement server. You can use subscription-manager to register.
#7 0.567
#7 0.606 Last metadata expiration check: 1:04:09 ago on Thu May 12 14:13:14 2022.
#7 0.721 No match for argument: shadow-utils-subid
#7 0.725 Error: Unable to find a match: shadow-utils-subid
Actually I think this BZ is my actual problem: https://bugzilla.redhat.com/show_bug.cgi?id=2084179