I am trying to use the docker ADD command within my Dockerfile which I am building via a pipeline.
My pipeline keeps failing when the docker build gets here:
ADD $PROJECT_ROOT/node_modules /server
ADD $PROJECT_ROOT/db /server
ADD $PROJECT_ROOT/env /server
ADD $PROJECT_ROOT/server /server
ADD $PROJECT_ROOT/package.json /server
ADD $PROJECT_ROOT/package-lock.json /server
ADD $PROJECT_ROOT/server.js /server
I get the error:
/var/lib/docker/165536.165536/tmp/docker-builder953599875/opt/atlassian/pipelines/agent/build/node_modules: no such directory
$PROJECT_ROOT is passed into my Dockerfile as an argument and is equal to the $BITBUCKET_CLONE_DIR variable.
Here's the pipeline step:
name: docker build
- docker build -t my-app . --build-arg ENV=staging --build-arg PROJECT_ROOT=$BITBUCKET_CLONE_DIR
- docker tag my-app my.cr.io/my-app
- docker save --output tmp-image.docker my.cr.io/my-app
Somehow, it looks like Docker is always appending the directory "/var/lib/docker/165536.165536/tmp/docker-builder953599875" to the beginning of the source path when using ADD. How do I fix this?
Hey Community! We’re willing to wager that quite a few of you not only use Bitbucket, but administer it too. Our team is excited to share that we’ll be releasing improvements throughout this month of...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events