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.

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

Make it possible for projects to have volumes #206

Open
jawher opened this issue May 3, 2015 · 2 comments
Open

Make it possible for projects to have volumes #206

jawher opened this issue May 3, 2015 · 2 comments

Comments

@jawher
Copy link
Contributor

jawher commented May 3, 2015

An example:

In the upcoming bazooka e2e (end to end tests):

  • The go test code places some files in a folder, say a .bazooka.yml and a couple .go files for example
  • The test code then starts a git daemon container to serve these files over the git:// protocol. The files directory is bind-mounted to the git container

This works if the test code is executed on the host, but not in bazooka, because the test code places the files in a directory in its own filesystem, which is not visible from the outside and cannot be mounted as a volume in another container.

@julienvey
Copy link
Member

would a simple syntax like services be enough ?

volumes:
  - /some/path/on/host:/a/container/path

and we juste add this when running docker run on the build container

@jawher
Copy link
Contributor Author

jawher commented May 23, 2015

I really don't like the idea of specifying host paths in the .bazooka.yml file.

I was thinking of something like:

volumes:
  - env_var_name:/a/container/path

Where bazooka would mount a host directory in the container under the specified path, while also exposing an env var with the specified name containing the said host path.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants