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.

Bug 1672403

Summary:	Rootless Podman segfaults when creating pods
Product:	Red Hat Enterprise Linux 8	Reporter:	Matthew Heon <mheon>
Component:	podman	Assignee:	Brent Baude <bbaude>
Status:	CLOSED CURRENTRELEASE	QA Contact:	atomic-bugs <atomic-bugs>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	8.0	CC:	ajia, ddarrah, dwalsh, igreen, jligon, jwboyer, lsm5, mheon, pthomas, smccarty, wchadwic, ypu
Target Milestone:	rc	Flags:	rule-engine: mirror+
Target Release:	8.0
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-06-14 01:32:15 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Matthew Heon 2019-02-04 21:00:05 UTC

Description of problem:

Rootless Podman segfaults when attempting to create a pod using the '--pod=new:' option for 'podman create' and 'podman run'


Version-Release number of selected component (if applicable):

podman 1.0.0

How reproducible:

100%

Steps to Reproduce:
1. As a normal user, run 'podman run -t -i --rm --pod=new:test1 fedora bash'

Actual results:

Podman segfaults

Expected results:

Podman successfully runs bash in a new container in a new pod

Additional info:

Works as expected for Podman as root

Originally tracked at https://github.com/containers/libpod/issues/2124

Comment 1 Matthew Heon 2019-02-04 21:01:58 UTC

This is a pretty nasty segfault, and in a feature we explicitly called out in the 1.0 release notes. It's fixed upstream, so a backport shouldn't be a problem.

Comment 4 Matthew Heon 2019-02-06 15:39:57 UTC

@Lokesh - backports to the 1.0 branch aren't done yet, will ping when they are available. The branch in question will definitely be https://github.com/containers/libpod/tree/v1.0 though

Comment 10 Joy Pu 2019-02-21 08:45:09 UTC

Can reproduce with podman-1.0.0-1.git82e8011.module+el8+2696+e59f0461.x86_64.rpm. And test with podman-1.0.0-2.git921f98f.module+el8+2784+9a0c1dfe.x86_64 the steps in comments #1 passed. So set this to verified. Details:
$ podman run -t -i --rm --pod=new:test1 fedora bash
[root@a6188878f326 /]# ls
bin  boot  dev  etc  home  lib  lib64  lost+found  media  mnt  opt  proc  root  run  sbin  srv  sys  tmp  usr  var