FS#68029 - [podman] lchown /usr/bin/write: invalid argument

Attached to Project: Arch Linux
Opened by Alexander von Gluck (kallisti5) - Monday, 28 September 2020, 14:10 GMT
Last edited by freswa (frederik) - Monday, 28 September 2020, 19:34 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To No-one
Architecture All
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
Trying to use podman results in the following:

Storing signatures
Error: error creating build container: The following failures happened while trying to pull image specified by "fedora:latest" based on search registries in .
.
"sha256:c7def56d621e45515fa3da89a47a1a272299b9b536fa8511a58c085dc51781b9": Error processing tar file(exit status 1): there might not be enough IDs available in the namespace (requested 0:5 for /usr/bin/write): lchown /usr/bin/write: invalid argument
* "registry.fedoraproject.org/fedora:latest": Error committing the finished image: error adding layer with blob "sha256:dd9f43919ba05f05d4f783c31e83e5e776c4f5d29dd72b9ec5056b9576c10053": Error processing tar file(exit status 1): there might not be enough IDs available in the namespace (requested 0:12 for /var/spool/mail): lchown /var/spool/mail: invalid argument
.
.


Additional info:
* community/podman 2.1.0-1 [installed]
* community/podman-docker 2.1.0-1 [installed]


Steps to reproduce:
* Install
* Attempt to use
This task depends upon

Closed by  freswa (frederik)
Monday, 28 September 2020, 19:34 GMT
Reason for closing:  Not a bug
Additional comments about closing:  Wiki includes necessary instructions.
Comment by Alexander von Gluck (kallisti5) - Monday, 28 September 2020, 14:16 GMT
An Arch user reported a similar issue here:
https://github.com/containers/podman/issues/2542#issuecomment-512634229

He listed a workaround of generating

killing podman
sudo touch /etc/sub{u,g}id
sudo usermod --add-subuids 10000-75535 $(whoami)
sudo usermod --add-subgids 10000-75535 $(whoami)
rm /run/user/$(id -u)/libpod/pause.pid

That seems to "fix" the issue. Just adding /etc/subuid + /etc/subgid isn't enough, you also have to kill podman and cleaup any running podman processes.
Comment by Alexander von Gluck (kallisti5) - Monday, 28 September 2020, 14:23 GMT
tldr: missing "subuid's and subgid's" results in podman not working.

Maybe a profile addition by podman around "checking for subuid's and subgui's" for the logged in user and generating them if needed?

Loading...