-
Notifications
You must be signed in to change notification settings - Fork 2.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Incorrect process UIDs with podman compose top
(running docker-compose
v2)
#22293
Comments
How did you get the Is this included into Podman 5.0 now? |
It's part of Compose V2 https://docs.docker.com/reference/cli/docker/compose/top/ |
Just to be sure, isn't this normal? I think the IDs reported are correct, as you're not running it inside Podman. Maybe I'm completely wrong here, but I did experiment with Docker rootless, and it couldn't really handle UID/GID-handling like Podman. |
I'm not running Docker, I'm running Podman, just using docker-compose V2 to talk to the Podman Rest API. If I'm not wrong this is possible since |
A friendly reminder that this issue had no activity for 30 days. |
When we execute ps(1) in the container and the container uses a userns with a different id mapping the user id field will be wrong. To fix this we must join the userns in such case. Fixes containers#22293 Signed-off-by: Paul Holzinger <[email protected]>
When we execute ps(1) in the container and the container uses a userns with a different id mapping the user id field will be wrong. To fix this we must join the userns in such case. Fixes containers#22293 Signed-off-by: Paul Holzinger <[email protected]> <MH: Fixed conflict in tests> Signed-off-by: Matt Heon <[email protected]>
Issue Description
I'm seeing the wrong UID on the output of
podman compose top
. I'm running rootless podman with rootless users inside the containers, but under my user ns (keepid
). The container user with UID1000
in this case is callednonroot
and my host uesr issamuel
.I'm new to podman so I have a lot to learn, let me know if this issue should be better on the
docker-compose
side.Steps to reproduce the issue
Describe the results you received
Podman top output (UID's inside the container:
Podman compose output (IT SHOWS ROOT!)
From the host perspective, the process show UID 1000
Describe the results you expected
I expected the UID shown in podman compose top to be 1000, as inside the containers and on the host.
podman info output
Podman in a container
No
Privileged Or Rootless
Rootless
Upstream Latest Release
Yes
Additional environment details
I'm on Fedora 39.
Additional information
No response
The text was updated successfully, but these errors were encountered: