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

share|improve this question

asked yesterday

NotSoShabby

16412

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

share|improve this question

asked yesterday

NotSoShabby

16412

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

share|improve this question

asked yesterday

NotSoShabby

16412

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

share|improve this question

asked yesterday

NotSoShabby

16412

share|improve this question

asked yesterday

NotSoShabby

16412

share|improve this question

share|improve this question

asked yesterday

NotSoShabby

16412

asked yesterday

NotSoShabby

16412

asked yesterday

NotSoShabby

16412

16412

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.

share|improve this answer

edited yesterday

answered yesterday

Siyu

894417

• 
  
  
  

  
  

  
  
  
  
  
  

  
  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
  yesterday
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  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
  yesterday
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  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
  yesterday
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  see updated answer
  – Siyu
  yesterday
  

  
  
  
  

add a comment | 

Your Answer

StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");

StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});

function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});


}
});

 

draft saved

draft discarded

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

Name

Email

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

Name

Email

Required, but never shown

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.

share|improve this answer

edited yesterday

answered yesterday

Siyu

894417

• 
  
  
  

  
  

  
  
  
  
  
  

  
  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
  yesterday
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  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
  yesterday
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  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
  yesterday
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  see updated answer
  – Siyu
  yesterday
  

  
  
  
  

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.

share|improve this answer

edited yesterday

answered yesterday

Siyu

894417

• 
  
  
  

  
  

  
  
  
  
  
  

  
  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
  yesterday
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  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
  yesterday
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  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
  yesterday
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  see updated answer
  – Siyu
  yesterday
  

  
  
  
  

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.

share|improve this answer

edited yesterday

answered yesterday

Siyu

894417

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.

share|improve this answer

edited yesterday

answered yesterday

Siyu

894417

share|improve this answer

share|improve this answer

edited yesterday

edited yesterday

edited yesterday

answered yesterday

Siyu

894417

answered yesterday

Siyu

894417

answered yesterday

Siyu

894417

894417

• 
  
  
  

  
  

  
  
  
  
  
  

  
  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
  yesterday
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  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
  yesterday
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  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
  yesterday
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  see updated answer
  – Siyu
  yesterday
  

  
  
  
  

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
  yesterday
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  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
  yesterday
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  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
  yesterday
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  see updated answer
  – Siyu
  yesterday
  

  
  
  
  

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
yesterday

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
yesterday

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
yesterday

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
yesterday

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
yesterday

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
yesterday

see updated answer
– Siyu
yesterday

see updated answer
– Siyu
yesterday

add a comment | 

 

draft saved

draft discarded

 

draft saved

draft discarded

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

Name

Email

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

Name

Email

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

Name

Email

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

Name

Email

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

Name

Email

Required, but never shown

Name

Name

Email

Required, but never shown

Email

Required, but never shown

Email

Required, but never shown

Email

Required, but never shown

Name

Name

Email

Required, but never shown

Email

Required, but never shown

Email

Required, but never shown

Email

Required, but never shown

This page is only for reference, If you need detailed information, please check here