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 1212058 - libseccomp requires kernel
Summary: libseccomp requires kernel
Keywords:
Status: CLOSED DUPLICATE of bug 1066136
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: libseccomp
Version: 7.2
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: rc
: ---
Assignee: Paul Moore
QA Contact: Virtualization Bugs
URL:
Whiteboard:
Depends On: 1065572
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-04-15 13:24 UTC by Lukáš Nykrýn
Modified: 2015-04-16 22:00 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of: 1065572
Environment:
Last Closed: 2015-04-16 22:00:55 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Lukáš Nykrýn 2015-04-15 13:24:04 UTC
We are rebasing systemd in 7.2 and we have the same problem as in fedora.


+++ This bug was initially created as a clone of Bug #1065572 +++

Description of problem:
libseccomp requires the kernel package. This means that any package containing a program linked to libseccomp will force the installation of the kernel package. One such package is systemd (in versions >= 209), which is often installed in containers and lighweight VMs which do not have a kernel. Installing the kernel (and dependent packages) is a very large overhead for the minimal installation.

I understand the reason for this dependency, but it doesn't really work: on one hand, seccomp does detect missing kernel capabilities, and on the other, even with the kernel package installed one can run an older kernel, since it is multi-installable.

Version-Release number of selected component (if applicable):
libseccomp-2.1.0-1.fc20.x86_64

How reproducible:
100%

--- Additional comment from Paul Moore on 2014-02-17 22:05:04 CET ---

Resolved in libseccomp-2.1.1-1.fc21.

This BZ is against Rawhide, do you see a need for this in F20 as well, or are you happy to see it in F21?

--- Additional comment from Zbigniew Jędrzejewski-Szmek on 2014-02-17 22:06:45 CET ---

F21 is enough, thanks.

--- Additional comment from Paul Moore on 2014-02-17 22:13:48 CET ---

Okay, once I see the updated package propagate out to my Rawhide system I'll consider this closed.

--- Additional comment from Jóhann B. Guðmundsson on 2014-02-18 11:58:18 CET ---

This should also be fixed in all the GA releases ( F19/F20 ). 

People are running containers there as well

--- Additional comment from Zbigniew Jędrzejewski-Szmek on 2014-02-18 14:01:27 CET ---

Yeah, but we have no intention of linking to libseccomp there.

--- Additional comment from Paul Moore on 2014-02-19 17:57:57 CET ---

Everything looks fine now on my Rawhide system:

# rpm -q libseccomp libseccomp-devel
libseccomp-2.1.1-1.fc21.x86_64
libseccomp-devel-2.1.1-1.fc21.x86_64
# rpm -qR libseccomp
/sbin/ldconfig
/sbin/ldconfig
libc.so.6()(64bit)
libc.so.6(GLIBC_2.14)(64bit)
libc.so.6(GLIBC_2.2.5)(64bit)
rpmlib(CompressedFileNames) <= 3.0.4-1
rpmlib(FileDigests) <= 4.6.0-1
rpmlib(PayloadFilesHavePrefix) <= 4.0-1
rtld(GNU_HASH)
rpmlib(PayloadIsXz) <= 5.2-1
# rpm -qR libseccomp-devel
/usr/bin/pkg-config
libc.so.6()(64bit)
libc.so.6(GLIBC_2.2.5)(64bit)
libc.so.6(GLIBC_2.3)(64bit)
libseccomp(x86-64) = 2.1.1-1.fc21
libseccomp.so.2()(64bit)
pkgconfig
rpmlib(CompressedFileNames) <= 3.0.4-1
rpmlib(FileDigests) <= 4.6.0-1
rpmlib(PayloadFilesHavePrefix) <= 4.0-1
rtld(GNU_HASH)
rpmlib(PayloadIsXz) <= 5.2-1

--- Additional comment from Paul Moore on 2014-02-25 21:08:32 CET ---

Comment 1 Václav Pavlín 2015-04-15 13:53:36 UTC
This is very important for container images we produce because we don't want to have Kernel there.

Comment 2 Paul Moore 2015-04-16 22:00:55 UTC

*** This bug has been marked as a duplicate of bug 1066136 ***


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