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 1784228 - Whitelist statx(2) in docker
Summary: Whitelist statx(2) in docker
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: docker
Version: 7.7
Hardware: s390x
OS: Linux
high
high
Target Milestone: rc
: 7.8
Assignee: Jindrich Novy
QA Contact: atomic-bugs@redhat.com
URL:
Whiteboard:
Depends On: 1762578
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-12-17 02:18 UTC by Yaakov Selkowitz
Modified: 2020-04-01 00:27 UTC (History)
9 users (show)

Fixed In Version: docker-1.13.1-152.git4ef4b30.el7_8
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-04-01 00:26:47 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
Patch for extras-rhel-7.8 (520 bytes, patch)
2019-12-17 02:48 UTC, Yaakov Selkowitz 		no flags Details | Diff
View All


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2020:1234 0 None None None 2020-04-01 00:27:43 UTC

Description Yaakov Selkowitz 2019-12-17 02:18:24 UTC 
libuv, a dependency of Node.js, uses the statx(2) syscall, which is currently causing issues when run within a container:

https://github.com/nodejs/help/issues/1983
https://github.com/docker/for-linux/issues/208
https://github.com/NobodyOnSE/moby/blob/b2a907c8cab64830c9e424eb1ec71e0429d326ff/profiles/seccomp/default.json

This is also the root cause of 1759152 and 1760184, which were worked around in the meantime albeit suboptimally.  RHEL8 nodejs (both 10 and 12) are similarly affected when run with docker on a RHEL7 host.
Comment 3 Yaakov Selkowitz 2019-12-17 02:48:11 UTC 
Created attachment 1645725 [details]
Patch for extras-rhel-7.8

As our RPM provides a secconf.json, this dist-git patch should suffice, but it probably would be better to also cherry-pick the upstream fix into our docker sources:

https://github.com/moby/moby/commit/f0694e968fe600efdf24ab0d3a1b0e887267aea2
Comment 5 Daniel Walsh 2019-12-17 14:08:15 UTC 
Any chance you can change to Podman?  Which comes with update seccomp.json.
Comment 6 Yaakov Selkowitz 2019-12-17 17:15:29 UTC 
No, the builders use docker.
Comment 14 Jindrich Novy 2019-12-23 18:48:03 UTC 
Patched also the seccomp.json directly in dist-git. All should be good now.
Comment 17 Alex Jia 2020-02-12 07:48:39 UTC 
This bug has been verified in docker-1.13.1-152.git4ef4b30.el7_8.x86_64 and docker-1.13.1-156.gitcccb291.el7_8.x86_64.

1. docker-1.13.1-152.git4ef4b30.el7_8.x86_64

[root@kvm-08-guest30 ~]# rpm -q docker
docker-1.13.1-152.git4ef4b30.el7_8.x86_64
[root@kvm-08-guest30 ~]# grep statx /etc/docker/seccomp.json
				"statx",
[root@kvm-08-guest30 ~]# docker run -ti -u 0 registry.access.redhat.com/rhscl/s2i-base-rhel7 bash
bash-4.2# rpm -qa|grep rh-nodejs10
rh-nodejs10-runtime-3.2-3.el7.x86_64
rh-nodejs10-nodejs-10.16.3-4.el7.x86_64
rh-nodejs10-npm-6.9.0-10.16.3.4.el7.x86_64
bash-4.2# scl enable rh-nodejs10 -- npm --version
6.9.0

2. docker-1.13.1-156.gitcccb291.el7_8.x86_64

[root@kvm-08-guest30 ~]# rpm -q docker
docker-1.13.1-156.gitcccb291.el7_8.x86_64
[root@kvm-08-guest30 ~]# grep statx /etc/docker/seccomp.json
				"statx",
[root@kvm-08-guest30 ~]# docker run -ti -u 0 registry.access.redhat.com/rhscl/s2i-base-rhel7 bash
bash-4.2# rpm -qa|grep rh-nodejs10
rh-nodejs10-runtime-3.2-3.el7.x86_64
rh-nodejs10-nodejs-10.16.3-4.el7.x86_64
rh-nodejs10-npm-6.9.0-10.16.3.4.el7.x86_64
bash-4.2# scl enable rh-nodejs10 -- npm --version
6.9.0
Comment 18 Alex Jia 2020-03-09 10:07:00 UTC 
Also verified in docker-1.13.1-161.git64e9980.el7_8.x86_64.
Comment 20 errata-xmlrpc 2020-04-01 00:26:47 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:1234
Note You need to log in before you can comment on or make changes to this bug.