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.
This is an incompatiblity with atomic-pkglayer and the docker `%post` - it's unaware that we're running inside a container.
https://github.com/GNOME/ostree/pull/212
will address this by allowing use of `rpm -Uvh docker.rpm` outside of a container.
Currently though in order to test the new Docker you'd need an updated tree.
We can probably fix this in docker though by having its %post detect if it's inside a container and not try to load the policy? Something like `if test ${container} = "docker"` ?
(In reply to Daniel Walsh from comment #6)
> Looks like you are trying to install an rpm package onto an atomic host?
Yes, using atomic-pkglayer to update docker RPM pacakges onto an Atomic Host.
(In reply to Colin Walters from comment #8)
> We can probably fix this in docker though by having its %post detect if it's
> inside a container and not try to load the policy? Something like `if test
> ${container} = "docker"` ?
Colin, do we plan to fix this on 7.2.4? if so, I will close the bug as VERIFIED, because except this failure, the atomic-pkglayer works well.
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, 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://rhn.redhat.com/errata/RHBA-2016-0578.html
Comment 14Red Hat Bugzilla
2023-09-14 03:19:22 UTC
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days