-
Notifications
You must be signed in to change notification settings - Fork 841
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
Set up buildroot permissions for non-root access #493
Comments
Hi there! We use Pivotal Tracker to provide visibility into what our team is working on. A story for this issue has been automatically created. The current status is as follows:
This comment, as well as the labels on the issue, will be automatically updated as the status in Tracker changes. |
dupe of #493 |
@vito Did you mean to point to another issue? Closing an issue as a duplicate of itself seems funky. Also, is there any workaround as of now, other than using sudo to chown the build dir? |
yep probably meant #403 |
In https://concourse.ci/running-tasks.html, it mentions that we can use the
USER
rule in our Dockerfile to control what user a task runs as. However, when doing so, that user doesn't have access to write into the build directory.For my immediate case, it means I cannot run
godep restore
on code that was placed in the build as an input. I also suspect it will mean that i cannot create/write to output directories from this task.Can concourse be made to change permissions on the build directory to the user specified in the dockerfile?
The text was updated successfully, but these errors were encountered: