projectatomic
Use docker api rather than docker binary
part of #407
will allow us to stop embedding docker binary inside our containers.
@containscafeine @rtnpro
I was looking at this before and finding out the best possible way to convert docker run / cli commands to it's respective daemon API call. Unfortunately I was unable to find such way.
May be out of the scope of atomicapp, but starting a Python library that actually converts for example: docker run blahblah -v foo:bar to the http api call would be awesome.
I tried searching for such a library but was unable to :(
@cdrage +1, sounds cool. And when we run the docker daemon in foreground, then with each CLI command, we can see the corresponding API call, so maybe we can use that. But that's in Go.
But in this case, will we not be using one of these?
The last time I checked, python only maintained docker-py, but now I can also see them working on engine-api in Go!
I think docker-py is what I thought we would end up using. It is what Ansible uses to run docker containers. If there is a feature missing that we need then we should possibly add it or understand why it doesn't make sense to implement.
@dustymabe @cdrage @rtnpro has some work been done in atomicapp using docker-py or has someone started working on it?
On Wed, Feb 24, 2016, 9:16 AM Dusty Mabe [email protected] wrote:
I think docker-py is what I thought we would end up using. It is what Ansible uses to run docker containers. If there is a feature missing that we need then we should possibly add it or understand why it doesn't make sense to implement.
— Reply to this email directly or view it on GitHub https://github.com/projectatomic/atomicapp/issues/445#issuecomment-188049224 .
@containscafeine any progress on this?
I opened up a feature request upstream that might be useful in this endeavor. https://github.com/docker/docker-py/issues/1031