-
-
Notifications
You must be signed in to change notification settings - Fork 3k
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
Boot2Docker: VOLUME prevents chown to have effect #1804
Comments
Sorry, I tried to fix the signed-off check.. it's #1806 now... |
cc @Luzifer PTAL — On Tue, Oct 6, 2015 at 1:33 PM, Christian Kniep notifications@github.com
|
Fixed by #2064 (Docker image volume fix and Sharness tests). |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hey there,
I like to tip my toe into ipfs, therefore I tried to create my own docker image - failed - and came to your very own dockerfile. :)
If I build and run the image, I get:
Which is caused by the fact that
VOLUME /data/ipfs
is done under the userroot
. Which creates a directory on the docker host, which is mounted into the container using the give user.By putting the line
VOLUME
underneath theUSER ipfs
line, it will work as expected. This might take effect due to newer docker version (I use 1.8).The text was updated successfully, but these errors were encountered: