-
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
podman pod create --uidmap patch #14344
Conversation
LGTM |
I think @vrothberg already added a test which should be enabled, podman/test/system/170-run-userns.bats Line 41 in 800a367
|
1 similar comment
I think @vrothberg already added a test which should be enabled, podman/test/system/170-run-userns.bats Line 41 in 800a367
|
ah I see @vrothberg @Luap99, should i just rm that skip and maybe add an inspect to see if the infra ctr has the mappings? |
LGTM |
Yes, that sounds good to me. Apologies for the late reply. |
5294ef2
to
ebe104e
Compare
podmans remote API does not marshal infra's spec due to the fact that if it did, all of those options would be available to the users on the command line. This means we need to manually map "backwards" some container spec items -> pod spec items before calling PodCreate, this was one of them that was forgotten resolves containers#14233 Signed-off-by: cdoern <[email protected]> Signed-off-by: cdoern <[email protected]>
@vrothberg PTAL |
/approve |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: cdoern, rhatdan, vrothberg 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 |
podmans remote API does not marshal infra's spec due to
the fact that if it did, all of those options would be available to
the users on the command line. This means we need to manually map "backwards"
some container spec items -> pod spec items before calling PodCreate, this was
one of them that was forgotten
This is a patch that will most likely be reverted (for a better solution) once the new API specgen format is implemented for pods.
resolves #14233
Signed-off-by: cdoern [email protected]
Does this PR introduce a user-facing change?