On 08/10/2015 19:04, Kapil Arya wrote:
I don't know all the details, but I guess, depending upon the exact interface, it might be possible to have a C++ wrapper around a non-C++ containerizer module. In a very naive approach, one simply fork/execs the "external" non-C++ containerizer script/program.... and sends instructions to it. Which is, as far as I can see, what the external containerizer does.
