pipework and non-native docker engine
helander opened this issue · 1 comments
Pipework is great and really useful. In many cases, typically in development scenarios my containers are running in a virtual machine on a Mac or Win laptop. I can control my containers using the native clients but when it comes to integration of pipework commands in my control flows I am lost, since they have to be run on the virtual machine, where I have no control from my native clients.
This is really not a pipework problem, but a problem on how to mix docker commands with command sequences to be executed on the docker engine host.
Maybe something like a "docker host-exec " ?
This could possibly be done by bypassing docker completely, but then there is no way to integrate it with docker-compose. As of now I am not able to use docker-compose since I need to integrate pipework and similar operations in my control flow.
Anyone that have suggestions?
Found out that I can do the things I wanted to do using docker run with --net=host and --pid=host.