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

Fixes #18907, pass in correct cwd value for hooks exe #18921

Conversation

fangpenlin
Copy link
Contributor

@fangpenlin fangpenlin commented Jun 16, 2023

Fixes #18907

This PR depends on containers/common#1514 to be merged. Sorry first time contributor, I am not sure what's the correct workflow to make changes in upstream common repo. I assume I should create a new PR in common repo first, then wait for a new release from common then update the vendor file in this repo to make it depends on the changes I made in common?

Does this PR introduce a user-facing change?

Hook executables invoked by podman run command now come with the correct working directory pointing to the container bundle directory

@openshift-ci openshift-ci bot added release-note do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. labels Jun 16, 2023
@fangpenlin fangpenlin changed the title WIP: Pass in correct cwd value for hooks exe WIP: Fixes #18907, pass in correct cwd value for hooks exe Jun 16, 2023
@fangpenlin fangpenlin changed the title WIP: Fixes #18907, pass in correct cwd value for hooks exe Fixes #18907, pass in correct cwd value for hooks exe Jun 17, 2023
@openshift-ci openshift-ci bot removed the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Jun 17, 2023
@fangpenlin fangpenlin force-pushed the fix-18907-set-correct-cwd-for-poststop-hook-exe branch from 0e32cc7 to 3e95216 Compare June 23, 2023 18:39
@fangpenlin fangpenlin force-pushed the fix-18907-set-correct-cwd-for-poststop-hook-exe branch from 3e95216 to dd81f7a Compare June 27, 2023 06:50
@fangpenlin
Copy link
Contributor Author

Updated PR with the new methods in common. Still waiting for a new common release. Do I need to add vendor changes in this PR by the way?

@rhatdan
Copy link
Member

rhatdan commented Jun 27, 2023

No you do not have to wait for the vendoring.

LGTM
/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 27, 2023
@rhatdan
Copy link
Member

rhatdan commented Jun 27, 2023

@containers/podman-maintainers PTAL

@rhatdan
Copy link
Member

rhatdan commented Jun 27, 2023

@vrothberg @Luap99 PTAL

@rhatdan
Copy link
Member

rhatdan commented Jun 27, 2023

@giuseppe PTAL

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 28, 2023
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jun 28, 2023

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: fangpenlin, 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 f739f8f into containers:main Jun 28, 2023
@fangpenlin fangpenlin deleted the fix-18907-set-correct-cwd-for-poststop-hook-exe branch June 28, 2023 06:36
@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 26, 2023
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Sep 26, 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
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Wrong CWD value set when calling OCI poststop hook executable
4 participants