Introduce a new interface, where CRS developers can provide a set of Docker containers the run directly on host (no need for DinD). We can let CRS developers provide a Docker compose YAML configuration.
Resource constraints can still be applied by using --cgroup-parent for memory limits, and the cpuset can stay the same (i.e. give the same cpuset to multiple containers when they belong to the same CRS).
Note this does not deprecate the DinD workflow, since this cannot handle container orchestration. All containers will be launched simultaneously from OSS-CRS via Docker compose.