Docker failed to build: ADD failed:
up vote
-1
down vote
favorite
I have the following volume for the app.
Docker compose file
registry-server:
build:
context: ./registry-server
dockerfile: Dockerfile
volumes:
- /jars
- /app/
- ./../registry-server/target:/jars
docker file
FROM openjdk:11-jre
MAINTAINER IG <ig@ig.com>
RUN apt-get update
RUN apt-get -y install netcat
ADD /jars/registry-server.jar /app/registry-server.jar
RUN chmod +x /app/registry-server.jar
I get error
ERROR: Service 'registry-server' failed to build: ADD failed: stat
/var/lib/docker/tmp/docker-builder823709495/jars/.jar: no such file or
directory
docker docker-compose dockerfile
add a comment |
up vote
-1
down vote
favorite
I have the following volume for the app.
Docker compose file
registry-server:
build:
context: ./registry-server
dockerfile: Dockerfile
volumes:
- /jars
- /app/
- ./../registry-server/target:/jars
docker file
FROM openjdk:11-jre
MAINTAINER IG <ig@ig.com>
RUN apt-get update
RUN apt-get -y install netcat
ADD /jars/registry-server.jar /app/registry-server.jar
RUN chmod +x /app/registry-server.jar
I get error
ERROR: Service 'registry-server' failed to build: ADD failed: stat
/var/lib/docker/tmp/docker-builder823709495/jars/.jar: no such file or
directory
docker docker-compose dockerfile
add a comment |
up vote
-1
down vote
favorite
up vote
-1
down vote
favorite
I have the following volume for the app.
Docker compose file
registry-server:
build:
context: ./registry-server
dockerfile: Dockerfile
volumes:
- /jars
- /app/
- ./../registry-server/target:/jars
docker file
FROM openjdk:11-jre
MAINTAINER IG <ig@ig.com>
RUN apt-get update
RUN apt-get -y install netcat
ADD /jars/registry-server.jar /app/registry-server.jar
RUN chmod +x /app/registry-server.jar
I get error
ERROR: Service 'registry-server' failed to build: ADD failed: stat
/var/lib/docker/tmp/docker-builder823709495/jars/.jar: no such file or
directory
docker docker-compose dockerfile
I have the following volume for the app.
Docker compose file
registry-server:
build:
context: ./registry-server
dockerfile: Dockerfile
volumes:
- /jars
- /app/
- ./../registry-server/target:/jars
docker file
FROM openjdk:11-jre
MAINTAINER IG <ig@ig.com>
RUN apt-get update
RUN apt-get -y install netcat
ADD /jars/registry-server.jar /app/registry-server.jar
RUN chmod +x /app/registry-server.jar
I get error
ERROR: Service 'registry-server' failed to build: ADD failed: stat
/var/lib/docker/tmp/docker-builder823709495/jars/.jar: no such file or
directory
docker docker-compose dockerfile
docker docker-compose dockerfile
asked Nov 11 at 19:18
Saurabh Kumar
5,3883590160
5,3883590160
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
up vote
0
down vote
Volumes are not available at build time. They are able at runtime. Your code seems to assume this.
if i put path to my jar directory direclty in docker file... i get out of context error. Any suggestions how to solve this ?
– Saurabh Kumar
Nov 11 at 19:44
is the jar located out of the build directory? you have to change build context so that it would be possible to address the file from that path "downwards" in the drectory tree
– Uku Loskit
Nov 11 at 21:10
add a comment |
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
0
down vote
Volumes are not available at build time. They are able at runtime. Your code seems to assume this.
if i put path to my jar directory direclty in docker file... i get out of context error. Any suggestions how to solve this ?
– Saurabh Kumar
Nov 11 at 19:44
is the jar located out of the build directory? you have to change build context so that it would be possible to address the file from that path "downwards" in the drectory tree
– Uku Loskit
Nov 11 at 21:10
add a comment |
up vote
0
down vote
Volumes are not available at build time. They are able at runtime. Your code seems to assume this.
if i put path to my jar directory direclty in docker file... i get out of context error. Any suggestions how to solve this ?
– Saurabh Kumar
Nov 11 at 19:44
is the jar located out of the build directory? you have to change build context so that it would be possible to address the file from that path "downwards" in the drectory tree
– Uku Loskit
Nov 11 at 21:10
add a comment |
up vote
0
down vote
up vote
0
down vote
Volumes are not available at build time. They are able at runtime. Your code seems to assume this.
Volumes are not available at build time. They are able at runtime. Your code seems to assume this.
answered Nov 11 at 19:24
Uku Loskit
29.9k86779
29.9k86779
if i put path to my jar directory direclty in docker file... i get out of context error. Any suggestions how to solve this ?
– Saurabh Kumar
Nov 11 at 19:44
is the jar located out of the build directory? you have to change build context so that it would be possible to address the file from that path "downwards" in the drectory tree
– Uku Loskit
Nov 11 at 21:10
add a comment |
if i put path to my jar directory direclty in docker file... i get out of context error. Any suggestions how to solve this ?
– Saurabh Kumar
Nov 11 at 19:44
is the jar located out of the build directory? you have to change build context so that it would be possible to address the file from that path "downwards" in the drectory tree
– Uku Loskit
Nov 11 at 21:10
if i put path to my jar directory direclty in docker file... i get out of context error. Any suggestions how to solve this ?
– Saurabh Kumar
Nov 11 at 19:44
if i put path to my jar directory direclty in docker file... i get out of context error. Any suggestions how to solve this ?
– Saurabh Kumar
Nov 11 at 19:44
is the jar located out of the build directory? you have to change build context so that it would be possible to address the file from that path "downwards" in the drectory tree
– Uku Loskit
Nov 11 at 21:10
is the jar located out of the build directory? you have to change build context so that it would be possible to address the file from that path "downwards" in the drectory tree
– Uku Loskit
Nov 11 at 21:10
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53252292%2fdocker-failed-to-build-add-failed%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown