-
Notifications
You must be signed in to change notification settings - Fork 32
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
Permission denied in entrypoint.sh #54
Comments
Does this problem still exist? |
Not sure to be honest. Will check and close if solved. |
Yes, it does. |
Thank for confirming and yes, I re-confirm, yes it does. |
dothebart
added a commit
that referenced
this issue
Apr 11, 2019
the suggested change will be available with ArangoDB 3.4.6 |
I solve this problem by adding 2 lines before
|
Yes, that's precisely what I did too. Thanks. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Just a quick note - I've been running locally the Dockerfile so that I can use it as a base image and have dumps and scripts executed and I've been getting this error
ERROR: for arangodb Cannot start service arangodb: b'OCI runtime create failed: container_linux.go:348: starting container process caused "exec: \\"/entrypoint.sh\\": permission denied": unknown'
I have resolved by adding the chmod line under the entrypoint statement as follows
I can see that you state in the doc that "if you are using the image as a base image please make sure to wrap any CMD in the exec form. Otherwise the default entrypoint will not do its bootstrapping work." but I am not sure that's the issue I've hit, mostly because I do not know what that means due to my.. ignorance. If that's the case please accept my apologies, point me to an example if you please, and do close this issue.
Otherwise, you might want to be aware of this issue..
The text was updated successfully, but these errors were encountered: