Currently, we hard-code the (single) name of the Docker container for a startup kit. This prevents running, e.g., multiple preflight checks or local trainings in parallel, or running local trainings while a swarm client is running on the same machine (assuming sufficient computational resources) without workarounds. We may want to change this.
AC:
Currently, we hard-code the (single) name of the Docker container for a startup kit. This prevents running, e.g., multiple preflight checks or local trainings in parallel, or running local trainings while a swarm client is running on the same machine (assuming sufficient computational resources) without workarounds. We may want to change this.
AC: