Differences when compiling in the dockerfile step vs in the bash

Hi, I am encountering a problem. I am running a make file from my dockerfile like this
WORKDIR /app/mydir/lib
RUN ./make.sh

It somehow runs different build commands from when i run up my docker like this:

sudo nvidia-docker run --rm -ti -p 5001:5001 mydocker5 bash
cd /app/mydir/lib
./make.sh

How do I begin to compare what is different with the two?

how about if you just run it in a “sh” instead of a “bash” shell? Maybe this is already the difference.

Also could try to run it like
docker run .... -w /app/mydir/lib mydocker5 ./make.sh

edit: sorry replied to the wrong post

Hi I tried
sudo nvidia-docker run --rm -ti -p 5001:5001 mydocker5 sh
cd /app/mydir/lib
./make.sh

and it gives the same result as

sudo nvidia-docker run --rm -ti -p 5001:5001 mydocker5 bash
cd /app/mydir/lib
./make.sh

docker run … -w /app/mydir/lib mydocker5 ./make.sh

Also gives the same (correct ) result.
But normally I run sudo nvidia-docker run --rm -ti -p 5001:5001 mydocker5
because in my docker file i have a CMD [ “mod_wsgi-express”, “start-server”, “–port”, “5001”, “–user”,
“apache”, “–group”, “root”, “–log-to-terminal”, “wsgi.py” ]

that i want to run that will use the compiled results from that make.sh which when run from the docker file is wrong…