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

podman pod create --uidmap patch #14344

Merged
merged 1 commit into from
Jun 2, 2022

Conversation

cdoern
Copy link
Contributor

@cdoern cdoern commented May 24, 2022

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?

None

@rhatdan
Copy link
Member

rhatdan commented May 24, 2022

LGTM
Although I am not sure how/why this works.

@Luap99
Copy link
Member

Luap99 commented May 25, 2022

I think @vrothberg already added a test which should be enabled,

skip_if_remote "remote --uidmap is broken (see #14233)"

1 similar comment
@Luap99
Copy link
Member

Luap99 commented May 25, 2022

I think @vrothberg already added a test which should be enabled,

skip_if_remote "remote --uidmap is broken (see #14233)"

@cdoern
Copy link
Contributor Author

cdoern commented May 25, 2022

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?

@TomSweeneyRedHat
Copy link
Member

LGTM
once you coordinate with @vrothberg

@vrothberg
Copy link
Member

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?

Yes, that sounds good to me. Apologies for the late reply.

@cdoern cdoern force-pushed the podCreate branch 2 times, most recently from 5294ef2 to ebe104e Compare June 1, 2022 13:15
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]>
@cdoern
Copy link
Contributor Author

cdoern commented Jun 1, 2022

@vrothberg PTAL

@rhatdan
Copy link
Member

rhatdan commented Jun 1, 2022

/approve

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jun 1, 2022
Copy link
Member

@vrothberg vrothberg left a comment

Choose a reason for hiding this comment

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

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Jun 2, 2022
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jun 2, 2022

[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 /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-merge-robot openshift-merge-robot merged commit e4e1006 into containers:main Jun 2, 2022
@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 21, 2023
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Sep 21, 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. release-note-none
Projects
None yet
Development

Successfully merging this pull request may close these issues.

remote pod create - custom user NS broken
6 participants