Docker compose-Mount volume on a few containers AND the host
up vote
1
down vote
favorite
Im trying to share data between a few containers and the host using docker-compose. I have a docker-compose.yml file that looks like this:
version: '3'
services:
base:
container_name: base
build:
context: .
dockerfile: BaseDockerfile
volumes:
- dependencies:/volumes/dependencies
romee:
container_name: romee
build:
context: .
dockerfile: RomeeDockerfile
environment:
- PYTHONPATH=/volumes/base_dependencies/
volumes:
- dependencies:/volumes/base_dependencies
volumes:
dependencies:
Now the volume "dependencies" is shared successfully between the containers, but I want to also share it with the host. How can I do that?
docker docker-compose
add a comment |
up vote
1
down vote
favorite
Im trying to share data between a few containers and the host using docker-compose. I have a docker-compose.yml file that looks like this:
version: '3'
services:
base:
container_name: base
build:
context: .
dockerfile: BaseDockerfile
volumes:
- dependencies:/volumes/dependencies
romee:
container_name: romee
build:
context: .
dockerfile: RomeeDockerfile
environment:
- PYTHONPATH=/volumes/base_dependencies/
volumes:
- dependencies:/volumes/base_dependencies
volumes:
dependencies:
Now the volume "dependencies" is shared successfully between the containers, but I want to also share it with the host. How can I do that?
docker docker-compose
add a comment |
up vote
1
down vote
favorite
up vote
1
down vote
favorite
Im trying to share data between a few containers and the host using docker-compose. I have a docker-compose.yml file that looks like this:
version: '3'
services:
base:
container_name: base
build:
context: .
dockerfile: BaseDockerfile
volumes:
- dependencies:/volumes/dependencies
romee:
container_name: romee
build:
context: .
dockerfile: RomeeDockerfile
environment:
- PYTHONPATH=/volumes/base_dependencies/
volumes:
- dependencies:/volumes/base_dependencies
volumes:
dependencies:
Now the volume "dependencies" is shared successfully between the containers, but I want to also share it with the host. How can I do that?
docker docker-compose
Im trying to share data between a few containers and the host using docker-compose. I have a docker-compose.yml file that looks like this:
version: '3'
services:
base:
container_name: base
build:
context: .
dockerfile: BaseDockerfile
volumes:
- dependencies:/volumes/dependencies
romee:
container_name: romee
build:
context: .
dockerfile: RomeeDockerfile
environment:
- PYTHONPATH=/volumes/base_dependencies/
volumes:
- dependencies:/volumes/base_dependencies
volumes:
dependencies:
Now the volume "dependencies" is shared successfully between the containers, but I want to also share it with the host. How can I do that?
docker docker-compose
docker docker-compose
asked Nov 19 at 10:23
NotSoShabby
17312
17312
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
up vote
1
down vote
accepted
The question is equivalent to how to specify a path of a named volume:
Solution:
volumes:
dependencies:
driver: local
driver_opts:
type: 'none'
o: 'bind'
device: '/abs/path/to/dependencies'
EDIT
The complete flow would be like,
Image: Dependency generator, at build time (docker build), generate dependency to /temp, then at run time (docker run / docker-compose up), cp -pr /temp /dependencies
, after that it can exit 0.
Can you explain the order that the mounting is happening? for example, if I already have that directory on the server, will it override the containers data?
– NotSoShabby
Nov 19 at 10:44
the host file will override the container data, this is desirable or not depending on how you share the dependency. How do you create them in the first place?
– Siyu
Nov 19 at 10:50
I wantto have one container creating the dependencies when on build and then other containers using them from the volume. I wanted to also be able to have access to that volume from the host
– NotSoShabby
Nov 19 at 11:17
see updated answer
– Siyu
Nov 19 at 12:36
add a comment |
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
1
down vote
accepted
The question is equivalent to how to specify a path of a named volume:
Solution:
volumes:
dependencies:
driver: local
driver_opts:
type: 'none'
o: 'bind'
device: '/abs/path/to/dependencies'
EDIT
The complete flow would be like,
Image: Dependency generator, at build time (docker build), generate dependency to /temp, then at run time (docker run / docker-compose up), cp -pr /temp /dependencies
, after that it can exit 0.
Can you explain the order that the mounting is happening? for example, if I already have that directory on the server, will it override the containers data?
– NotSoShabby
Nov 19 at 10:44
the host file will override the container data, this is desirable or not depending on how you share the dependency. How do you create them in the first place?
– Siyu
Nov 19 at 10:50
I wantto have one container creating the dependencies when on build and then other containers using them from the volume. I wanted to also be able to have access to that volume from the host
– NotSoShabby
Nov 19 at 11:17
see updated answer
– Siyu
Nov 19 at 12:36
add a comment |
up vote
1
down vote
accepted
The question is equivalent to how to specify a path of a named volume:
Solution:
volumes:
dependencies:
driver: local
driver_opts:
type: 'none'
o: 'bind'
device: '/abs/path/to/dependencies'
EDIT
The complete flow would be like,
Image: Dependency generator, at build time (docker build), generate dependency to /temp, then at run time (docker run / docker-compose up), cp -pr /temp /dependencies
, after that it can exit 0.
Can you explain the order that the mounting is happening? for example, if I already have that directory on the server, will it override the containers data?
– NotSoShabby
Nov 19 at 10:44
the host file will override the container data, this is desirable or not depending on how you share the dependency. How do you create them in the first place?
– Siyu
Nov 19 at 10:50
I wantto have one container creating the dependencies when on build and then other containers using them from the volume. I wanted to also be able to have access to that volume from the host
– NotSoShabby
Nov 19 at 11:17
see updated answer
– Siyu
Nov 19 at 12:36
add a comment |
up vote
1
down vote
accepted
up vote
1
down vote
accepted
The question is equivalent to how to specify a path of a named volume:
Solution:
volumes:
dependencies:
driver: local
driver_opts:
type: 'none'
o: 'bind'
device: '/abs/path/to/dependencies'
EDIT
The complete flow would be like,
Image: Dependency generator, at build time (docker build), generate dependency to /temp, then at run time (docker run / docker-compose up), cp -pr /temp /dependencies
, after that it can exit 0.
The question is equivalent to how to specify a path of a named volume:
Solution:
volumes:
dependencies:
driver: local
driver_opts:
type: 'none'
o: 'bind'
device: '/abs/path/to/dependencies'
EDIT
The complete flow would be like,
Image: Dependency generator, at build time (docker build), generate dependency to /temp, then at run time (docker run / docker-compose up), cp -pr /temp /dependencies
, after that it can exit 0.
edited Nov 19 at 12:36
answered Nov 19 at 10:39
Siyu
1,316620
1,316620
Can you explain the order that the mounting is happening? for example, if I already have that directory on the server, will it override the containers data?
– NotSoShabby
Nov 19 at 10:44
the host file will override the container data, this is desirable or not depending on how you share the dependency. How do you create them in the first place?
– Siyu
Nov 19 at 10:50
I wantto have one container creating the dependencies when on build and then other containers using them from the volume. I wanted to also be able to have access to that volume from the host
– NotSoShabby
Nov 19 at 11:17
see updated answer
– Siyu
Nov 19 at 12:36
add a comment |
Can you explain the order that the mounting is happening? for example, if I already have that directory on the server, will it override the containers data?
– NotSoShabby
Nov 19 at 10:44
the host file will override the container data, this is desirable or not depending on how you share the dependency. How do you create them in the first place?
– Siyu
Nov 19 at 10:50
I wantto have one container creating the dependencies when on build and then other containers using them from the volume. I wanted to also be able to have access to that volume from the host
– NotSoShabby
Nov 19 at 11:17
see updated answer
– Siyu
Nov 19 at 12:36
Can you explain the order that the mounting is happening? for example, if I already have that directory on the server, will it override the containers data?
– NotSoShabby
Nov 19 at 10:44
Can you explain the order that the mounting is happening? for example, if I already have that directory on the server, will it override the containers data?
– NotSoShabby
Nov 19 at 10:44
the host file will override the container data, this is desirable or not depending on how you share the dependency. How do you create them in the first place?
– Siyu
Nov 19 at 10:50
the host file will override the container data, this is desirable or not depending on how you share the dependency. How do you create them in the first place?
– Siyu
Nov 19 at 10:50
I wantto have one container creating the dependencies when on build and then other containers using them from the volume. I wanted to also be able to have access to that volume from the host
– NotSoShabby
Nov 19 at 11:17
I wantto have one container creating the dependencies when on build and then other containers using them from the volume. I wanted to also be able to have access to that volume from the host
– NotSoShabby
Nov 19 at 11:17
see updated answer
– Siyu
Nov 19 at 12:36
see updated answer
– Siyu
Nov 19 at 12:36
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%2f53372553%2fdocker-compose-mount-volume-on-a-few-containers-and-the-host%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