-
-
Notifications
You must be signed in to change notification settings - Fork 557
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
docker-compose builds as root #90
Comments
And I forgot to mention, my operating system is ubuntu-16.04 -- xfce desktop |
Out of the box, Docker on Ubuntu requires root, see: https://askubuntu.com/questions/477551/how-can-i-use-docker-without-sudo |
That I fixed when I tried my first docker program. I made a small and I built image using the following: the but I still have the problem that I created the issue for. |
@smishr4 On our side, other than running an initial |
I think probably something to do the way docker creates the directory on linux machine. https://stackoverflow.com/questions/33509752/docker-compose-creates-file-owned-by-root Anyways instead of doing Doing this works too:
Thanks |
First, thank you very much for this wonderful node-boilerplate, It really does cover a long tech stack which I am trying to complete bit by bit.
Problem which I encountered when I tried to run this as described, simply did:
cd nodejs-api-starter
docker-compose up
And I get this error:
api_1 | EACCES: permission denied, mkdir 'build/emails'
api_1 | EACCES: permission denied, mkdir 'build/emails'
...
and so on.
The problem here is that the build directory created by running build.js through docker-compose is root protected and doesn't allow any further changes, so the build process fails and finally the ./build/server.js is unavailable. I can manually create a build directory that is not root protected and repeat the process then it works. Probably something to do with docker's functioning and my lack of experience in working with it. Can you help me figure out a work around?
screenshot:
http://i.imgur.com/ckiomWY.png
The text was updated successfully, but these errors were encountered: