Support for alternative container runtimes
!54 (merged) enables the support for alternative
container runtimes: different implementations of the container logic, with different APIs than nodeos_config.
We need to come up with a flexible design to allow users to take advantage of this feature. In particular, on a platform were we don't have any setuid binary, we can still allow the NRM to run using just a
dummy runtime that launches commands without actually creating containers.
The question is: should this be a configuration option for the daemon or for each command ?
for the daemon ** static for the entire daemon run, so cannot change without restarting the daemon ** added to the config options of the daemon itself ** doesn't require immediate change to the command line API, depending on the runtime (dummy & cuttr are fine, runc might be more complicated)
for the command ** allows users to run different techs at the same time ** one more field to the manifest, not sure if that make much sense though
In both cases, we also need to change the CI/tests to ensure that all of it works.
I'm ignoring the more complex issue of changing the entire bin/cmd API to support a different container spec like OCI, as it would probably require moving the cmd to an API more similar to docker and runc, and make radical changes to the manifest management.