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.

Sign up for GitHub

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

Jump to bottom

Remove recursive chown in content-init #2899

Closed
svenefftinge opened this issue Jan 14, 2021 · 0 comments · Fixed by #2900
Closed

Remove recursive chown in content-init #2899

svenefftinge opened this issue Jan 14, 2021 · 0 comments · Fixed by #2900
Assignees
@svenefftinge
Labels
component: content-service component: ws-daemon
Milestone
January 2021

Comments

@svenefftinge
Copy link
Member

For historical reasons we do a recursive chown in the initialization logic. We seem to not need that anymore and in can cause trouble and surprises so we should remove it.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@svenefftinge svenefftinge

Labels
component: content-service component: ws-daemon
Projects
None yet
Milestone
January 2021
Development

Successfully merging a pull request may close this issue.

[content-init] remove unneeded chown gitpod-io/gitpod
2 participants
@svenefftinge @csweichel