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.

Description of problem:
[root@localhost packages]# rpm -i filesystem-3.8-3.el8.x86_64.rpm 
error: unpacking of archive failed on file /proc: cpio: chown failed - No such file or directory
error: filesystem-3.8-3.el8.x86_64: install failed

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

How reproducible:
Always

Steps to Reproduce:
1. run a rootless container 
2.
3.

Actual results:
fail to update the package

Expected results:
Having the filesystem package updated without error

Additional info:
Looks similar to this closed BZ against Fedora
https://bugzilla.redhat.com/show_bug.cgi?id=1723266

rpm should skip chowning /proc and /sys when running in a user namespace.

> rpm should skip chowning /proc and /sys when running in a user namespace.

rpm doesn't have any concept of magic directories that should be treated specially, quite intentionally.

How does one determine being inside a user namespace?

(In reply to Panu Matilainen from comment #1)
> > rpm should skip chowning /proc and /sys when running in a user namespace.
> 
> rpm doesn't have any concept of magic directories that should be treated
> specially, quite intentionally.
> 
> How does one determine being inside a user namespace?

As commented by Giuseppe Scrivano in [1]

"$ cat /proc/self/uid_map 
         0          0 4294967295
$ cat /proc/self/gid_map 
         0          0 4294967295

If the content of these files is different than "0 0 4294967295" then you are running in a user namespace where the root user is not mapped to root in the initial user namespace."


Additionally, Debarshi Ray kindly commneted that this same issue was solved
in toolbox 0.0.99.3 by this commit [2].

[1]: https://bugzilla.redhat.com/show_bug.cgi?id=1723266#c11
[2]: https://github.com/containers/toolbox/commit/7542f5fc867b57bf3dc67bbae02cc09ccc0b5df2

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