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.
Created attachment 1548698[details]
config.json for failing container
podman, built from recent master (aba3a8423682635f98e4e3fd4d9a3e5a36667aeb) on rhel8:
testuser$ podman run --rm alpine_labels date
Error: container create failed: cannot specify gid= mount options for unmapped gid in rootless containers
: internal libpod error
Works fine with podman-1.0.0-2.git921f98f.module+el8+2785+ff8a053f.x86_64
At Matt's suggestion, looking at the OCI spec yields:
$ jq . < ~/.local/share/containers/storage/overlay-containers/f292eae1edd581dda6db479b10a4184004f89b9c2533484d8bd64cb3c01098ad/userdata/config.json | grep -5 gid=
"nosuid",
"noexec",
"newinstance",
"ptmxmode=0666",
"mode=0620",
"gid=5" <<<<<<<<<<<<<<<<<<<<<
]
},
{
"destination": "/dev/mqueue",
"type": "mqueue",
(full config.json attached, after processing with jq to make it readable)
Those values suspiciously match ones in vendor/github.com/opencontainers/runtime-tools/generate/generate.go
A container created by older podman (1.0.0-2.etc, see above) does not contain the string 'gid=' in its config.json
FWIW the same podman produces a similar config.json on f29 (containing 'gid=') but on this system it works fine.
Can reproduce with give runc and podman version. Test with following package and it works well. Details:
$ podman run --rm alpine date
Sun Sep 29 02:56:00 UTC 2019
$ rpm -qa |grep -e ^podman-1 -e runc
podman-1.4.2-5.module+el8.1.0+4240+893c1ab8.x86_64
runc-1.0.0-60.rc8.module+el8.1.0+4081+b29780af.x86_64
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-2019:3403
Created attachment 1548698 [details] config.json for failing container podman, built from recent master (aba3a8423682635f98e4e3fd4d9a3e5a36667aeb) on rhel8: testuser$ podman run --rm alpine_labels date Error: container create failed: cannot specify gid= mount options for unmapped gid in rootless containers : internal libpod error Works fine with podman-1.0.0-2.git921f98f.module+el8+2785+ff8a053f.x86_64 At Matt's suggestion, looking at the OCI spec yields: $ jq . < ~/.local/share/containers/storage/overlay-containers/f292eae1edd581dda6db479b10a4184004f89b9c2533484d8bd64cb3c01098ad/userdata/config.json | grep -5 gid= "nosuid", "noexec", "newinstance", "ptmxmode=0666", "mode=0620", "gid=5" <<<<<<<<<<<<<<<<<<<<< ] }, { "destination": "/dev/mqueue", "type": "mqueue", (full config.json attached, after processing with jq to make it readable) Those values suspiciously match ones in vendor/github.com/opencontainers/runtime-tools/generate/generate.go A container created by older podman (1.0.0-2.etc, see above) does not contain the string 'gid=' in its config.json FWIW the same podman produces a similar config.json on f29 (containing 'gid=') but on this system it works fine.