which one could be the best piece of code to start? Eixo::Docker seems to be interesting.
Looking at the various interaction events provided, I also believe Eixo::Docker would provide all the basics we need. Together with the db entries for various options on images, containers and events, then all is needed is sewing them together to a limited but rock solid e-smith commands. For now I would suggest we leave anything that as to do with images out of the equation (pull/build/commit etc), and work with a sample image to get things done.
One thing we do need to keep in mind is the fast pase in which Docker being developed and if this pase is followed by Eixo::Docker and if this library is stable and maintained for the long term.
@stephdl, what do you think pls?
guest