Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.

Bug 1702705

Summary:	rootless podman always fail if selinux is disabled
Product:	[Fedora] Fedora	Reporter:	Levente Farkas <lfarkas>
Component:	podman	Assignee:	Lokesh Mandvekar <lsm5>
Status:	CLOSED ERRATA	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	29	CC:	bbaude, dwalsh, lsm5, mheon
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	podman-1.3.1-1.git7210727.fc30 podman-1.3.1-1.git7210727.fc29	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-05-20 01:03:55 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 Levente Farkas 2019-04-24 14:04:33 UTC

even the most basic containers like mariadb or mongo failed on a system where try to use rootless podman and selinux is disabled. why podman depend on a totally independent system like selinux?

wasn't the main point of podman over docker that it can be run rootless?

do you still wonder why most people disable selinux? just because if someone can't find a reason for some failor that it's used to be selinux.

here is my upstream bug report:
https://github.com/containers/libpod/issues/3001

Comment 1 Daniel Walsh 2019-04-24 15:38:50 UTC

Downgrade to the previous version of runc.  We have a fix working its way into runc, which should be merged today, and then we will package it up.

Or you could enable SELinux :^)

Comment 2 Daniel Walsh 2019-04-24 16:00:30 UTC

Could you grab the package from https://bodhi.fedoraproject.org/updates/FEDORA-2019-6174b47003 and test it out. If it fixes the issue, could you update the Karma.

Fixed in runc-1.0.0-92.dev.gitc1b8c57.fc29

Comment 3 Levente Farkas 2019-04-24 17:48:15 UTC

not working.
see my comment in #1699326.

Comment 4 Fedora Update System 2019-05-17 17:20:33 UTC

podman-1.3.1-1.git7210727.fc29 has been submitted as an update to Fedora 29. https://bodhi.fedoraproject.org/updates/FEDORA-2019-fe6ef87556

Comment 5 Fedora Update System 2019-05-17 17:20:44 UTC

podman-1.3.1-1.git7210727.fc30 has been submitted as an update to Fedora 30. https://bodhi.fedoraproject.org/updates/FEDORA-2019-a0ddb8df76

Comment 6 Fedora Update System 2019-05-18 00:54:16 UTC

podman-1.3.1-1.git7210727.fc30 has been pushed to the Fedora 30 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2019-a0ddb8df76

Comment 7 Fedora Update System 2019-05-18 04:11:29 UTC

podman-1.3.1-1.git7210727.fc29 has been pushed to the Fedora 29 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2019-fe6ef87556

Comment 8 Fedora Update System 2019-05-20 01:03:55 UTC

podman-1.3.1-1.git7210727.fc30 has been pushed to the Fedora 30 stable repository. If problems still persist, please make note of it in this bug report.

Comment 9 Fedora Update System 2019-06-05 02:01:13 UTC

podman-1.3.1-1.git7210727.fc29 has been pushed to the Fedora 29 stable repository. If problems still persist, please make note of it in this bug report.