docker entrypoint running bash script gets permission denied

Question

I m trying to dockerize my node js app  When the container is built I want it to run a git clone and then start the node server  Therefore I put these operations in a  sh script  And run the script as a single command in the ENTRYPOINT   FROM ubuntu 14 04  RUN apt-get update  amp  amp  apt-get install -y build-essential libssl-dev gcc curl npm git   install gcc 4 9 RUN apt-get install -y software-properties-common python-software-properties RUN add-apt-repository -y ppa ubuntu-toolchain-r test RUN apt-get update RUN apt-get install -y libstdc  -4 9-dev   install newst nodejs RUN curl -sL https   deb nodesource com setup 4 x   sudo -E bash - RUN apt-get install -y nodejs  RUN mkdir -p  usr src app WORKDIR  usr src app  ADD package json  usr src app  RUN npm install  ADD docker-entrypoint sh  usr src app   EXPOSE 8080  ENTRYPOINT    usr src app docker-entrypoint sh      My docker-entrypoint sh looks like this   git clone git  lt repo gt  git git add remote upstream git  lt upstream repo gt  git   usr bin node server js   After building this image and run   docker run --env NODE ENV development -p 8080 8080 -t -i  lt image gt    I m getting    docker  Error response from daemon  oci runtime error  exec    usr src app docker-entrypoint sh   permission denied    I shell into the container and the permission of docker-entrypoint sh is   -rw-r--r-- 1 root root 292 Aug 10 18 41 docker-entrypoint sh   three questions    Does my bash script have wrong syntax  How do I change the permission of a bash file before adding it into an image  What s the best way to run multiple git commands in entrypoint without using a bash script    Thanks

User · Answer

An executable file needs to have permissions for execute set before you can execute it.

In your machine where you are building the docker image (not inside the docker image itself) try running:

ls -la path/to/directory

The first column of the output for your executable (in this case docker-entrypoint.sh) should have the executable bits set something like:

-rwxrwxr-x

If not then try:

chmod +x docker-entrypoint.sh

and then build your docker image again.

Docker uses it's own file system but it copies everything over (including permissions bits) from the source directories.

User · Answer

If you do not use DockerFile  you can simply add permission as command line argument of the bash   docker run -t  lt image gt    bin bash -c  chmod  x  usr src app docker-entrypoint sh   usr src app docker-entrypoint sh

User · Answer

This is a bit stupid maybe but the error message I got was Permission denied and it sent me spiralling down in a very wrong direction to attempt to solve it   Here for example  I haven t even added any bash script myself  I think one is added by nodejs image which I use  FROM node 14 9 0  I was wrongly running to expose connect the port on my local  docker run -p 80 80  name      this is wrong   which gives  usr local bin docker-entrypoint sh  8  exec     Permission denied  But you shouldn t even have a dot in the end  it was added to documentation of another projects docker image by misstake  You should simply run  docker run -p 80 80  name   I like Docker a lot but it s sad it has so many gotchas like this and not always very clear error messages

User · Answer

Dot     This problem take with me more than 3 hours finally   I just tried the problem was in removing dot from the end just   problem was docker run  -p 3000 80 --rm --name test-con test-app      usr local bin docker-entrypoint sh  8  exec     Permission denied  just remove dot from the end of your command line   docker run  -p 3000 80 --rm --name test-con test-app

User · Answer

Permission denied  prevents your script from being invoked at all  Thus  the only syntax that could be possibly pertinent is that of the first line  the  shebang    which should look like    usr bin env bash  or    bin bash  or similar depending on your target s filesystem layout  Most likely the filesystem permissions not being set to allow execute  It s also possible that the shebang references something that isn t executable  but this is far less likely  Mooted by the ease of repairing the prior issues      The simple reading of  docker  Error response from daemon  oci runtime error  exec    usr src app docker-entrypoint sh   permission denied       is that the script isn t marked executable   RUN   chmod     x     usr src app docker-entrypoint sh     will address this within the container  Alternately  you can ensure that the local copy referenced by the Dockerfile is executable  and then use COPY  which is explicitly documented to retain metadata

User · Answer

This is an old question asked two years prior to my answer  I am going to post what worked for me anyways   In my working directory I have two files  Dockerfile  amp  provision sh  Dockerfile   FROM centos 6 8    put the script in the  root directory of the container COPY provision sh  root    execute the script inside the container RUN  root provision sh  EXPOSE 80    Default command CMD    bin bash     provision sh      usr bin env bash  yum upgrade   I was able to make the file in the docker container executable by setting the file outside the container as executable chmod 700 provision sh then running docker build

User · Answer

I faced same issue  amp  it resolved by   ENTRYPOINT   sh     docker-entrypoint sh     For the Dockerfile in the original question it should be like   ENTRYPOINT   sh     usr src app docker-entrypoint sh

User · Answer

If you still get Permission denied errors when you try to run your script in the docker s entrypoint  just try DO NOT use the shell form of the entrypoint  Instead of  ENTRYPOINT   bin watcher write ENTRYPOINT   quot   bin watcher quot    https   docs docker com engine reference builder  entrypoint

[bash] docker entrypoint running bash script gets "permission denied"

Examples related to bash

Examples related to shell

Examples related to docker