Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Docker volume mounting too strict #34

Closed
goord opened this issue Apr 3, 2019 · 0 comments · Fixed by #39
Closed

Docker volume mounting too strict #34

goord opened this issue Apr 3, 2019 · 0 comments · Fixed by #39
Assignees
@sverhoeven

Comments

@goord
Copy link
Collaborator

goord commented Apr 3, 2019

For projects using a shared large forcing dataset, the architecture of mounting a single input and output directory in the docker container is too strict. We want to be able to mount arbitrary shared volumes and reference those in the initialization file.
@sverhoeven sverhoeven self-assigned this Jul 10, 2019
sverhoeven added a commit that referenced this issue Jul 10, 2019
@sverhoeven
Added extra_volumes argument to BmiClientDocker
6661451 
Allows to attach extra volumes to Docker container

Fixes #34
@sverhoeven sverhoeven mentioned this issue Jul 10, 2019
Merged
@goord goord closed this as completed in #39 Jul 10, 2019
goord pushed a commit that referenced this issue Jul 10, 2019
@sverhoeven @goord
Added extra_volumes argument to BmiClientDocker (#39)
9c6aac4 
Allows to attach extra volumes to Docker container

Fixes #34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@sverhoeven sverhoeven

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Added extra_volumes argument to BmiClientDocker eWaterCycle/grpc4bmi
2 participants
@sverhoeven @goord