Replies: 8 comments 2 replies
-
I believe |
Beta Was this translation helpful? Give feedback.
-
What do you mean by NFS? The filesystem the user's home directory is mapped to is Btrfs, if that is the concern. |
Beta Was this translation helpful? Give feedback.
-
Ah, looks like that's not necessarily a requirement. Googling about suggests that you could be seeing something related to systemd/systemd#21952 (or, alternatively, systemd-homed has not configured subuid/subgid ranges for the users in question at all?) |
Beta Was this translation helpful? Give feedback.
-
The problem is around the /etc/subuid and /etc/subgid fields not being populated. |
Beta Was this translation helpful? Give feedback.
-
you are allowed to have only one uid/gid with systemd-homed. All you can do is to set |
Beta Was this translation helpful? Give feedback.
-
So is this simply unsolvable for now, due to the way both of these programs work? |
Beta Was this translation helpful? Give feedback.
-
I am a bit confused with this situation, the Systemd issue @mheon presented is closed and I would assume that this issue is fixed, but it seems like not? I do not even know which software (Podman or Homed) should be considered as breaking? I would assume that distributions will adopt Homed in the future as it really has it's upsides, does that mean that Podman would break for all of those users? |
Beta Was this translation helpful? Give feedback.
-
In order to setup a user namespace, users have to have entries in /etc/subuid and /etc/subgid, If systemd-homed is not populating these filed with entries then users can not create UIDs different then their default UID, which breaks all containers. If you think this is a bug then it needs to be reported to systemd, there is nothing that the podman team can do. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Issue Description
Command
podman run -v -dt -p 8080:80/tcp docker.io/library/httpd
fails with:Steps to reproduce the issue
Steps to reproduce the issue
podman run -v -dt -p 8080:80/tcp docker.io/library/httpd
.Describe the results you received
Describe the results you received
Describe the results you expected
Container runs normally as it does launching it as a superuser.
podman info output
Podman version:
Kernel:
OS: Arch Linux (x64)
Podman in a container
No
Privileged Or Rootless
Rootless
Upstream Latest Release
Yes
Additional environment details
No response
Additional information
The output of
userdbctl
:It works fine for users not managed by systemd-homed.
Beta Was this translation helpful? Give feedback.
All reactions