-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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
Podman play kube ignores USER (rootless) #9609
Comments
I can confirm this. I have found the same issue in Running an image with |
I'll take this one. |
A friendly reminder that this issue had no activity for 30 days. |
@mheon did you ever get a chance to work on thisone? |
Negative, can take a look next week
…On Sat, Apr 17, 2021 at 07:56 Daniel J Walsh ***@***.***> wrote:
@mheon <https://github.com/mheon> did you ever get a chance to work on
thisone?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#9609 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AB3AOCCMLYRCQLMDQYCDVATTJFZPLANCNFSM4YS2CMZQ>
.
|
A friendly reminder that this issue had no activity for 30 days. |
Currently if a user runs an image with a user specified or exposed ports with podman play kube, the fields are ignored. Fixed: containers#9609 Signed-off-by: Daniel J Walsh <[email protected]>
Work around containers/podman#9609 (which causes the USER set in the Dockerfile to be ignored) in Podman 3.2.3. (The issue is fixed in Podman 3.3.) Co-authored-by: Richard Su <[email protected]>
Work around containers/podman#9609 (which causes the USER set in the Dockerfile to be ignored) in Podman 3.2.3. (The issue is fixed in Podman 3.3.) Co-authored-by: Richard Su <[email protected]>
Work around containers/podman#9609 (which causes the USER set in the Dockerfile to be ignored) in Podman 3.2.3. (The issue is fixed in Podman 3.3.) Co-authored-by: Richard Su <[email protected]>
Is this a BUG REPORT or FEATURE REQUEST? (leave only one on its own line)
/kind bug
Description
The
podman play kube
command does not use the user specified in the DockerfileSteps to reproduce the issue:
podman play kube test.yaml
podman play kube
:Describe the results you received:
The user should be the same ("testuser" in this case) with or without
podman play kube
.Describe the results you expected:
The user is "root" when I use
podman play kube
.Additional information you deem important (e.g. issue happens only occasionally):
Output of
podman version
:Output of
podman info --debug
:Package info (e.g. output of
rpm -q podman
orapt list podman
):Have you tested with the latest version of Podman and have you checked the Podman Troubleshooting Guide?
Yes
The text was updated successfully, but these errors were encountered: