Bug 1804782

Summary:	Unprivileged podman using: cannot lock /etc/passwd; try again later.
Product:	Red Hat Enterprise Linux 8	Reporter:	Konstantin Ryadov <kryadov>
Component:	podman	Assignee:	Tom Sweeney <tsweeney>
Status:	CLOSED DUPLICATE	QA Contact:	atomic-bugs <atomic-bugs>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	8.1	CC:	bbaude, dwalsh, gscrivan, jligon, jnovy, lsm5, mheon
Target Milestone:	rc
Target Release:	8.0
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-02-19 16:48:49 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 Konstantin Ryadov 2020-02-19 15:55:52 UTC

Description of problem:
Unable to operate with /etc/passwd, /etc/group and others from podman centos7/8 container when running under unprivileged user.

Version-Release number of selected component (if applicable):
Red Hat Enterprise Linux release 8.1 (Ootpa)

How reproducible:
Install and update RHEL 8.1 to the latest updates with "dnf update".

Steps to Reproduce:
1. "dnf update"
2. "dnf install podman"
3. "podman -v" => podman version 1.6.4
4. "adduser test" => login as test
5. "testpodman run -it --rm centos:8 /bin/bash"
6. "[root@2135a6a15a0f /]# adduser user" =>
adduser: /etc/passwd.14: lock file already used
adduser: cannot lock /etc/passwd; try again later.

Actual results:
adduser: /etc/passwd.14: lock file already used
adduser: cannot lock /etc/passwd; try again later.

Expected results:
No errors.

Additional info:
Problem is not reproduced on clean RHEL 8.1 installation without updates and under "root" user.

Comment 1 Matthew Heon 2020-02-19 16:46:41 UTC

I think this may be a known (and already fixed) fuse-overlayfs issue; tagging Giuseppe to make sure

Comment 2 Giuseppe Scrivano 2020-02-19 16:48:49 UTC

it is already tracked here: https://bugzilla.redhat.com/show_bug.cgi?id=1802907

*** This bug has been marked as a duplicate of bug 1802907 ***