Skip to content
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

Setting users in pod.yaml #2957

Closed
Fodoj opened this issue Apr 16, 2019 · 11 comments
Closed

Setting users in pod.yaml #2957

Fodoj opened this issue Apr 16, 2019 · 11 comments
Assignees
Labels
do-not-close Good First Issue This issue would be a good issue for a first time contributor to undertake. kind/feature Categorizes issue or PR as related to a new feature. locked - please file new issue/PR Assist humans wanting to comment on an old issue or PR with locked comments. stale-issue

Comments

@Fodoj
Copy link
Contributor

Fodoj commented Apr 16, 2019

/kind feature

Description

I'd love to be able to set a user for container inside pod.yaml, with securityContext. Is that already possible? I tried with runAsUser but it didnt change the user.

@openshift-ci-robot openshift-ci-robot added the kind/feature Categorizes issue or PR as related to a new feature. label Apr 16, 2019
@mheon
Copy link
Member

mheon commented Apr 16, 2019

Should be possible, but entirely possible we haven't wired that field in yet.

@Fodoj
Copy link
Contributor Author

Fodoj commented Apr 16, 2019

@mheon is that the complete code of parsing yaml and converting it to OCI spec and passing it to pod creation? https://github.com/containers/libpod/blob/master/cmd/podman/play_kube.go

@mheon
Copy link
Member

mheon commented Apr 16, 2019

Yes, all the play kube code lives in that file now

@baude
Copy link
Member

baude commented Aug 2, 2019

@lsm5 we can talk about this next week

@vrothberg
Copy link
Member

Ping, any movement on it? We could add a tag to get the community implement it?

@lsm5
Copy link
Member

lsm5 commented Oct 2, 2019

@vrothberg nothing so far from my side, and can't say at this point when I can get to it.

@vrothberg vrothberg added Contributor Wanted Good First Issue This issue would be a good issue for a first time contributor to undertake. labels Oct 2, 2019
@github-actions
Copy link

github-actions bot commented Nov 4, 2019

This issue had no activity for 30 days. In the absence of activity or the "do-not-close" label, the issue will be automatically closed within 7 days.

@rhatdan
Copy link
Member

rhatdan commented Nov 4, 2019

@haircommander Any chance you could look at this? Or maybe I will grab it.

@haircommander
Copy link
Collaborator

Yeah I'd like to get #4265 in, then start unifying the namespace workflow for pods

@vrothberg
Copy link
Member

Friendly ping.

@rhatdan
Copy link
Member

rhatdan commented Feb 17, 2020

From my reading of the code, I think this is implemented, reopen if I am mistaken.

@rhatdan rhatdan closed this as completed Feb 17, 2020
@github-actions github-actions bot added the locked - please file new issue/PR Assist humans wanting to comment on an old issue or PR with locked comments. label Sep 23, 2023
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Sep 23, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
do-not-close Good First Issue This issue would be a good issue for a first time contributor to undertake. kind/feature Categorizes issue or PR as related to a new feature. locked - please file new issue/PR Assist humans wanting to comment on an old issue or PR with locked comments. stale-issue
Projects
None yet
Development

No branches or pull requests

8 participants