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.
Bug 1806044 - 'yum -y install buildah fuse-overlayfs --exclude container-selinux' throws error
Summary: 'yum -y install buildah fuse-overlayfs --exclude container-selinux' throws error
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: buildah
Version: 8.2
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: 8.2
Assignee: Jindrich Novy
QA Contact: atomic-bugs@redhat.com
Gabriela Nečasová
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-02-21 21:17 UTC by Dennis Kliban
Modified: 2020-11-04 21:36 UTC (History)
13 users (show)

Fixed In Version: container-tools-rhel8-8020120200501055448.ffd2803a
Doc Type: Enhancement
Doc Text:
.Installing Podman does not require `container-selinux` With this enhancement, the installation of the `container-selinux` package is now optional during the container build. As a result, Podman has fewer dependencies on other packages.
Clone Of:
Environment:
Last Closed: 2020-07-21 15:31:54 UTC
Type: Bug
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2020:3053 0 None None None 2020-07-21 15:32:28 UTC

Description Dennis Kliban 2020-02-21 21:17:13 UTC
Description of problem:

I have the following in my Containerfile:

RUN useradd build; \
    yum -y update; \
    yum -y reinstall shadow-utils; \
    yum -y install buildah fuse-overlayfs --exclude container-selinux; \
    rm -rf /var/cache /var/log/dnf* /var/log/yum.*

I get the following error when I build a container using it:

Error: 
 Problem: package buildah-1.11.6-4.module_el8.1.0+272+3e64ee36.x86_64 requires container-selinux, but none of the providers can be installed
  - conflicting requests
  - package container-selinux-2:2.107-2.module_el8.1.0+237+63e26edc.noarch is excluded
  - package container-selinux-2:2.124.0-1.module_el8.1.0+272+3e64ee36.noarch is excluded
  - package container-selinux-2:2.94-1.git1e99f1d.module_el8.1.0+236+34fc7673.noarch is excluded
(try to add '--skip-broken' to skip uninstallable packages or '--nobest' to use not only best candidate packages)

Comment 1 Daniel Mach 2020-02-24 12:36:30 UTC
I believe the error you're getting is expected.

buildah *requires* container-selinux on RHEL 8:
$ dnf repoquery --requires buildah
...
container-selinux
...


That's why when you exclude container-selinux, buildah is no longer installable due to broken deps.

Comment 2 Dennis Kliban 2020-02-25 01:41:12 UTC
Lokesh Mandvekar, is this expected behavior for EL8?

Comment 3 Lokesh Mandvekar 2020-02-25 13:50:39 UTC
(In reply to Dennis Kliban from comment #2)
> Lokesh Mandvekar, is this expected behavior for EL8?

Jindrich owns the RHEL packages now, he'll check it out..

Comment 4 Jindrich Novy 2020-02-26 13:48:47 UTC
Looking at Fedora buildah I see these deps are relaxed:

Recommends: container-selinux
Recommends: slirp4netns >= 0.3-0
Recommends: fuse-overlayfs

while in RHEL there are hard dependencies:

Requires: container-selinux
Requires: slirp4netns >= 0.4.0-1
Requires: fuse-overlayfs
Requires: libvarlink

I lean for at least container-selinux and libvarlink being soft dependencies. As I see no reason why they should be hard deps. Same applies for fuse-overlayfs if we want to have rootless support optional which I don't think is a good idea.

Dan, do you agree?

Comment 5 Brian McLaughlin 2020-02-28 13:32:35 UTC
I downloaded and used the scratch build yesterday and ran into the following error during installation:

tldr;
- package runc-1.0.0-64.rc9.module_el8.1.0+272+3e64ee36.x86_64 requires container-selinux >= 2:2.2-2, but none of the providers can be installed

-----

Step 7/24 : RUN dnf -y install /tmp/buildah-1.11.6-8.el8.x86_64.rpm --exclude container-selinux
 ---> Running in b10fe43e17a1
Failed to set locale, defaulting to C.UTF-8
CentOS-8 - AppStream                            1.0 MB/s | 6.5 MB     00:06    
CentOS-8 - Base                                 2.8 MB/s | 5.0 MB     00:01    
CentOS-8 - Extras                               4.3 kB/s | 2.1 kB     00:00    
Error: 
 Problem: package buildah-1.11.6-8.el8.x86_64 requires runc >= 1.0.0-26, but none of the providers can be installed
  - package runc-1.0.0-64.rc9.module_el8.1.0+272+3e64ee36.x86_64 requires container-selinux >= 2:2.2-2, but none of the providers can be installed
  - conflicting requests
  - package container-selinux-2:2.107-2.module_el8.1.0+237+63e26edc.noarch is excluded
  - package container-selinux-2:2.124.0-1.module_el8.1.0+272+3e64ee36.noarch is excluded
  - package container-selinux-2:2.94-1.git1e99f1d.module_el8.1.0+236+34fc7673.noarch is excluded
  - package runc-1.0.0-55.rc5.dev.git2abd837.module_el8.1.0+236+34fc7673.x86_64 is excluded
  - package runc-1.0.0-60.rc8.module_el8.1.0+237+63e26edc.x86_64 is excluded
(try to add '--skip-broken' to skip uninstallable packages or '--nobest' to use not only best candidate packages)
ERROR: Service 'pulp-api' failed to build: The command '/bin/sh -c dnf -y install /tmp/buildah-1.11.6-8.el8.x86_64.rpm --exclude container-selinux' returned a non-zero code: 1

Comment 6 Dennis Kliban 2020-02-28 14:36:08 UTC
It looks like runc should stop having a hard requirement on container-selinux. Could we get a scratch build of runc without that dependency?

Comment 7 Jindrich Novy 2020-02-28 16:07:46 UTC
I see this in the spec file:

* Wed Oct 25 2017 Dan Walsh <dwalsh> - 1.0.0-17.rc4.gitaea4f21
- Add container-selinux prerequires to make sure runc is labeled correctly

Is that needed or I can remove the container-selinux from Requires?

Comment 8 Daniel Walsh 2020-03-02 13:13:14 UTC
It should be Recommended not Required.  But for runc, it should probably be removed altogether
as long as podman, buildah, cri-o recommend container-selinux.

Comment 20 Alex Jia 2020-05-18 16:32:48 UTC
There is no hard requirement on container-selinux for buildah-1.14.8-2.module+el8.2.1+6462+4149b287 and runc-1.0.0-66.rc10.module+el8.2.1+6462+4149b287.

[root@kvm-06-guest04 ~]# rpm -qR runc-1.0.0-66.rc10.module+el8.2.1+6462+4149b287.x86_64.rpm
criu
libc.so.6()(64bit)
libc.so.6(GLIBC_2.14)(64bit)
libc.so.6(GLIBC_2.2.5)(64bit)
libc.so.6(GLIBC_2.4)(64bit)
libc.so.6(GLIBC_2.7)(64bit)
libpthread.so.0()(64bit)
libpthread.so.0(GLIBC_2.2.5)(64bit)
libpthread.so.0(GLIBC_2.3.2)(64bit)
libseccomp.so.2()(64bit)
rpmlib(CompressedFileNames) <= 3.0.4-1
rpmlib(FileDigests) <= 4.6.0-1
rpmlib(PayloadFilesHavePrefix) <= 4.0-1
rpmlib(PayloadIsXz) <= 5.2-1
rtld(GNU_HASH)

[root@kvm-06-guest04 ~]# rpm -qR buildah-1.14.8-2.module+el8.2.1+6462+4149b287.x86_64.rpm
containers-common
libassuan.so.0()(64bit)
libc.so.6()(64bit)
libc.so.6(GLIBC_2.14)(64bit)
libc.so.6(GLIBC_2.2.5)(64bit)
libc.so.6(GLIBC_2.4)(64bit)
libdevmapper.so.1.02()(64bit)
libdevmapper.so.1.02(Base)(64bit)
libdevmapper.so.1.02(DM_1_02_97)(64bit)
libdl.so.2()(64bit)
libdl.so.2(GLIBC_2.2.5)(64bit)
libgpg-error.so.0()(64bit)
libgpgme.so.11()(64bit)
libgpgme.so.11(GPGME_1.0)(64bit)
libgpgme.so.11(GPGME_1.1)(64bit)
libpthread.so.0()(64bit)
libpthread.so.0(GLIBC_2.2.5)(64bit)
libpthread.so.0(GLIBC_2.3.2)(64bit)
libseccomp.so.2()(64bit)
rpmlib(CompressedFileNames) <= 3.0.4-1
rpmlib(FileDigests) <= 4.6.0-1
rpmlib(PayloadFilesHavePrefix) <= 4.0-1
rpmlib(PayloadIsXz) <= 5.2-1
rtld(GNU_HASH)
runc >= 1.0.0-26
slirp4netns >= 0.3-0

Comment 22 errata-xmlrpc 2020-07-21 15:31:54 UTC
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://access.redhat.com/errata/RHSA-2020:3053


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