I'm pretty new to the bash/shell script world, I'm trying to do the below and it could be pretty simple but I wasn't able to figure out the command, would be great if someone could help me out here and also point me to some documentation wrt to shell script topics. Thank you in advance.
My build.sh and Dockerfile resides under a folder called .settings and this folder lives directly under the app root. Now inside my build.sh and Dockerfile when I refer something like $(pwd) or COPY . /apps/ it might not work since my build.sh and Dockerfile does not live directly under the app root.
What command I can use in this scenario inside the files that I referenced above. Hope I made it clear. Once again this could be very simple since I'm a newbie in this arena I find it a little difficult.
inside build.sh, reference to $(pwd)
docker run \
-u root \
--rm \
-v $(pwd):/app \ ----> this $(pwd) references the application root, but if I
move this build.sh inside a folder called .settings then the $(pwd) context
would change and I still want to refer it to the root.
<MYIMAGE NAME FROM LOCAL REPO>
The last arg to
docker build
, often something likedocker build .
is the build context in docker. This directory is sent to the server where the build runs and allCOPY
andADD
commands are performed using this context. These commands do not run on the client, and docker is a client/server application, so anything not in that context simply doesn't exist for the purpose of building an image.So in the above example,
docker build .
the current directory is the build context and if that's run while you're inside of the.settings
directory, only those files are part of the build context. Therefore yourbuild.sh
script needs to pass a different directory, and also reference where theDockerfile
is inside of that build context. That would look like:When you do this, all of the
COPY
andADD
commands will now be relevant to parent directory, so you may need to adjust yourDockerfile
to compensate.For your
$(pwd)
reference, you can eithercd ..
before running yourdocker run
command or update the command to look like: