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

Handle image user and exposed ports in podman play kube #10383

Merged
merged 1 commit into from
May 27, 2021

Conversation

rhatdan
Copy link
Member

@rhatdan rhatdan commented May 18, 2021

Currently if a user runs an image with a user specified or
exposed ports with podman play kube, the fields are ignored.

Fixed: #9609

Signed-off-by: Daniel J Walsh [email protected]

@openshift-ci
Copy link
Contributor

openshift-ci bot commented May 18, 2021

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: rhatdan

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label May 18, 2021
@TomSweeneyRedHat
Copy link
Member

Test system is not at all happy with you today @rhatdan

@rhatdan rhatdan force-pushed the kube branch 4 times, most recently from 8dd2f58 to bbb0e12 Compare May 20, 2021 19:16
@rhatdan
Copy link
Member Author

rhatdan commented May 24, 2021

@containers/podman-maintainers PTAL

@baude
Copy link
Member

baude commented May 24, 2021

LGTM

return nil, err
}

if len(s.Expose) == 0 {
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

should we regenerate if len(exposed) != len(s.Expose) too?

@rhatdan rhatdan force-pushed the kube branch 2 times, most recently from 2d13c1b to 18f7b6b Compare May 25, 2021 17:04
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]>
@jwhonce
Copy link
Member

jwhonce commented May 27, 2021

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label May 27, 2021
@@ -182,6 +183,19 @@ func ToSpecGen(ctx context.Context, opts *CtrSpecGenOptions) (*specgen.SpecGener
if imageData.Config.WorkingDir != "" {
s.WorkDir = imageData.Config.WorkingDir
}
if s.User == "" {
s.User = imageData.Config.User
}
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should we really be setting the user to the value found in the image? That sounds like it might get twisted, or am I misreading this?

@openshift-merge-robot openshift-merge-robot merged commit 3d8f371 into containers:master May 27, 2021
@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
approved Indicates a PR has been approved by an approver from all required OWNERS files. lgtm Indicates that a PR is ready to be merged. locked - please file new issue/PR Assist humans wanting to comment on an old issue or PR with locked comments.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Podman play kube ignores USER (rootless)
5 participants