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 issue also occurs with RHEL-9.0.0-20210725.d.3. Package versions tested:
containers-common-1.3.1-1.el9.x86_64
libseccomp-2.5.0-5.el9.x86_64
podman-3.3.0-0.6.el9.x86_64
+++ This bug was initially created as a clone of Bug #1985499 +++
Fedora 35 and RHEL 9 Beta will first attempt to use the clone3 system call for thread creation.
$ podman run fedora:rawhide rpm -q glibc
glibc-2.33.9000-50.fc35.x86_64
$ podman run fedora:rawhide python3 -c 'import threading; threading.Thread(None, lambda: 0).start()'
Traceback (most recent call last):
File "<string>", line 1, in <module>
File "/usr/lib64/python3.10/threading.py", line 928, in start
_start_new_thread(self._bootstrap, ())
RuntimeError: can't start new thread
strace from outside the container shows the problematic EPERM error:
2667529 clone3({flags=CLONE_VM|CLONE_FS|CLONE_FILES|CLONE_SIGHAND|CLONE_THREAD|CLONE_SYSVSEM|CLONE_SETTLS|CLONE_PARENT_SETTID|CLONE_CHILD_CLEARTID, child_tid=0x7fd5c687f910, parent_tid=0x7fd5c687f910, exit_signal=0, stack=0x7fd5c607f000, stack_size=0x7fff00, tls=0x7fd5c687f640}, 88) = -1 EPERM (Operation not permitted)
This bug has been verified on containers-common-1.4.0-8.module+el9beta+12229+194de70a.
[root@kvm-08-guest28 ~]# cat /etc/redhat-release
Red Hat Enterprise Linux release 9.0 Beta (Plow)
[root@kvm-08-guest28 ~]# rpm -q containers-common libseccomp podman
containers-common-1.4.0-8.module+el9beta+12229+194de70a.x86_64
libseccomp-2.5.0-5.el9.x86_64
podman-3.3.0-0.19.module+el9beta+12229+194de70a.x86_64
[root@kvm-08-guest28 ~]# podman run fedora:rawhide python3 -c 'import threading; threading.Thread(None, lambda: 0).start()'
[root@kvm-08-guest28 ~]# echo $?
0
[root@kvm-08-guest28 ~]# podman ps -a
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
4b86b9497e60 registry.fedoraproject.org/fedora:rawhide python3 -c import... 15 seconds ago Exited (0) 15 seconds ago nifty_fermat
[root@kvm-08-guest28 ~]# podman run fedora:rawhide python3 -c "import os; os.system('ls')"
bin
boot
dev
etc
home
lib
lib64
lost+found
media
mnt
opt
proc
root
run
sbin
srv
sys
tmp
usr
var