Cannot run script added to existing docker container

Question

I have a container that is running with no issues. I added a bash script to compliment a couple other scripts already in the container. The docker image copy 2 scripts to /usr/local/bin and they can be accessed with docker exec -c container-name existingscript.

I added my own script to the same directory and when running the same command I get an error that exec cannot run the script: no file or directory,script not located in $PATH. I check path and sure enough, /usr/local/bin is listed. I checked permissions and the script is 755.

I then open an interactive shell with docker exec -it mycontainer bash and run /usr/local/bin/myscript and it runs with no problem.

Why can I not run the script from outside the container like I can the other two (that were included in the image). All three have almost the same functions a day do not use any special programs, one lists files, one adds files, one reads the file.

The base is Ubuntu.

EDIT: Found where I was running into the issue. Provided the answer in case anyone else happens to make the same mistake.

EDIT-2: So the script that came with the docker image to perform a couple common functions calls the image not the container so my adding the scripts to the container had no effect on the script which was why I kept getting the no file or directory error.

The line in the script in question was: docker run --rm -v "$(pwd)/config":/path/to/file -ti image_name:latest" mynewscript $@

Of course that ran against the image and NOT the container.

Once I noticed that I tried running it with exec instead of run and it ran without error, like so:

docker exec -it container_name mynewscript

Answer 1

While I was adding snippets to help explain the issue I found the problem and the solution.

So I access the scripts inside the container from the host with another script that allows you to do different things based on switch case. The scripts are called against the docker image and not the container so the script I added does not actually exist in the image.

I modified the script to call the container instead of the image and it works as expected.

EDIT: I updated the question with the answer but I am adding it here as well:

So the script that came with the docker image to perform a couple common functions calls the image not the container so my adding the scripts to the container had no effect on the script which was why I kept getting the no file or directory error.

The line in the script in question was:

docker run --rm -v "$(pwd)/config":/path/to/file -ti image_name:latest" mynewscript $@

Of course that ran against the image and NOT the container.

Once I noticed that I tried running it with exec instead of run and it ran without error, like so:

docker exec -it container_name mynewscript

Answer 2

The reason is "/usr/local/bin" not in your script's $PATH, you can use /usr/local/bin/myscript explicitly in your script. Or export $PATH first in the script.