We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
If builds run docker commands and mount in volumes, files are written as root, due to Docker's root-only-ness.
This means that subsequent builds fail with permission errors because they can't git clean the files.
git clean
The text was updated successfully, but these errors were encountered:
More details here moby/moby#3124
Sorry, something went wrong.
I just stumbled on this very issue. My workaround is to build an image ADDing the files instead of mounting a volume on a generic image.
A terrible hack that we have as a workaround is to use the docker socket to chown the files in a post-command hook:
post-command
#!/bin/bash set -eu docker run -it -v $(pwd):/project busybox chown -R 498.496 /project
No branches or pull requests
If builds run docker commands and mount in volumes, files are written as root, due to Docker's root-only-ness.
This means that subsequent builds fail with permission errors because they can't
git clean
the files.The text was updated successfully, but these errors were encountered: