drip
drip copied to clipboard
Documentation for use with Docker
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?