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

Readd mounting volumes in workingdir #1609

Merged
merged 1 commit into from
Nov 24, 2019

Conversation

chmouel
Copy link
Member

@chmouel chmouel commented Nov 23, 2019

Mounting volume was dropped when we did the large refactoring in
d7f492c which basically making
it ineffective and fails when not running as root.

Readding it in there

Closes #1608

/cc @imjasonh

Changes

Submitter Checklist

These are the criteria that every PR should meet, please check them off as you
review them:

Release Notes

Fix workingdir-init to mount the volumes when starting the initContainer.

@googlebot googlebot added the cla: yes Trying to make the CLA bot happy with ppl from different companies work on one commit label Nov 23, 2019
@tekton-robot tekton-robot added the size/M Denotes a PR that changes 30-99 lines, ignoring generated files. label Nov 23, 2019
@chmouel chmouel force-pushed the issue-1608-permission-denied branch from f5cff36 to f824728 Compare November 23, 2019 08:55
@chmouel
Copy link
Member Author

chmouel commented Nov 23, 2019

/retest

Copy link
Member

@imjasonh imjasonh left a comment

Choose a reason for hiding this comment

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

Sounds like we could use an integration test for this. I can add one after this or you can add one in this PR, up to you.

Thanks for catching this!

pkg/pod/workingdir_init_test.go Show resolved Hide resolved
Mounting volume was dropped when we did the large refactoring in
d7f492c which basically making
it ineffective and fails when not running as root.

Readding it in there

Closes tektoncd#1608

Signed-off-by: Chmouel Boudjnah <[email protected]>
@chmouel chmouel force-pushed the issue-1608-permission-denied branch from f824728 to d9030d2 Compare November 24, 2019 12:11
@chmouel
Copy link
Member Author

chmouel commented Nov 24, 2019

@imjasonh good point on the integration test, but this make me wonder, do we. need the workingdir ? since it seems that nobody has realised it wasn't and nothing catastrophic has been discovered since then without it ?

@imjasonh
Copy link
Member

Nobody may have noticed it was broken in the past few days, but most people don't run so aggressively from head either (plus, Kubecon).

If we decide to change the behavior, we should do it slowly over a couple releases with ample notice, but I don't really think we would since it's easy enough to support (when I'm not breaking it! 🤣)

/lgtm
/approve

@tekton-robot tekton-robot added the lgtm Indicates that a PR is ready to be merged. label Nov 24, 2019
@tekton-robot
Copy link
Collaborator

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: ImJasonH

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

@tekton-robot tekton-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Nov 24, 2019
@tekton-robot tekton-robot merged commit 9a4ec2e into tektoncd:master Nov 24, 2019
@chmouel chmouel deleted the issue-1608-permission-denied branch November 24, 2019 20:46
@afrittoli
Copy link
Member

@imjasonh good point on the integration test, but this make me wonder, do we. need the workingdir ? since it seems that nobody has realised it wasn't and nothing catastrophic has been discovered since then without it ?

I think the implicit mounts are quite handy to pass content between containers.
If /workspace/ wasn't there I would end up mounting a shared folder, so it's nice to have it done by Tetkon automatically :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. cla: yes Trying to make the CLA bot happy with ppl from different companies work on one commit lgtm Indicates that a PR is ready to be merged. size/M Denotes a PR that changes 30-99 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Permission denied when checking out source to /workspace
5 participants