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

Documentation for use with Docker #93

Open
spiffytech opened this issue Nov 18, 2015 · 0 comments
Open

Documentation for use with Docker #93

spiffytech opened this issue Nov 18, 2015 · 0 comments

Comments

@spiffytech
Copy link

I'm trying to use Drip in conjunction with short-lived Docker containers (think running a container that does 'lein repl' against my current working directory).

I can't figure out how Drip keeps track of its running JVMs, so each Docker container instance starts blind to the JVMs previous containers' Drips have spun up.

I have Docker rigged to create the Drip JVM in the host's process namespace (docker run --pid=host), so every container instance sees the latent JVMs. I also have ~/.drip mounted to a persisten volume, so each container instance has that data from previous containers.

But still, when I spin up a new Docker container, Drip inside it doesn't see any of the latent JVMs.

How does Drip keep track of its latent JVMs, so I can make that data persist between Docker containers?

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

No branches or pull requests

1 participant