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

Do not use tmpcopyup for user-specified tmpfs mounts #1413

Closed
wants to merge 1 commit into from

Conversation

mheon
Copy link
Member

@mheon mheon commented Sep 5, 2018

This is not Docker's behavior, and can trigger a runc bug related to tmpcopyup

This is not Docker's behavior, and can trigger a runc bug related
to tmpcopyup

Signed-off-by: Matthew Heon <[email protected]>
@baude
Copy link
Member

baude commented Sep 5, 2018

LGTM

@rhatdan
Copy link
Member

rhatdan commented Sep 6, 2018

👎 Definately not. We want this behaviour. What is it breaking? I fixed the latest version of runc to be able to work with this.

@rhatdan rhatdan closed this Sep 6, 2018
@mheon
Copy link
Member Author

mheon commented Sep 6, 2018

@rhatdan Was requested at openshift/installer#207 - it sounds like it might not be fully necessary, as @mrunalp is getting a runc built with appropriate patches to fix the issue

@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 27, 2023
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Sep 27, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
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.

3 participants