-
Notifications
You must be signed in to change notification settings - Fork 644
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
volume from doesn't appear to work #73
Comments
With the This The next version will provide more flexibility when binding to volumes (e.g. also local ones). |
Ok, that wasn't clear that the had to refer to an image created by this plugin. I'm trying to refer to an image already running in a container named 'maven'. I'm really looking for docker's --volume-from functionality. |
that functionality doesn't currently exist but i think that could be easily added. an additional element (maybe |
Externally running containers can be specified via their names in the <link> and <volume> section. They will be looked up after the plugin tried to resolve the dependencies internally. That way you can easily restart only the container you are working on right now and the dependencies will be picked up later. - pulled fine grained query methods out of DockerAccess into QueryService - added coarse grained list/inspect methods to DockerAccess - introduced model objects as proxies to JSON responses - refactored RunService to accept DocerAccess instance via 'initialize' method - allow linking/mounting from external containers - account for external data volume containers - extracted state information into it's own class - Use 'ServiceHub' as central access point for services Signed-off-by: Jae Gangemi <[email protected]>
fixed in 0.13.2 |
Fix NPE for newly initialized git repo
I start a maven container and give it the name 'maven' using docker's --name option. In my pom.xml I've configured my image as follows:
When I run maven I get the following error:
If I run taylodl/wls-mydomain using the docker run option "--volumes-from maven" then everything runs as I expect and the volumes are mounted where I expect. I was expecting to accomplish the same thing.
The text was updated successfully, but these errors were encountered: