Starling CLI deploy single containers + networks

[mhl787156]

Starling CLI currently runs docker-compose files using the deploy command with the file given by -f. This will cause the docker-compose to run as default with the default specified network, and run in the terminal.

This should be enhanced by

• Running Docker-compose in daemon mode (with some method of getting hold of logs, and killing the currently active docker-compose instance). Assumption that only one docker-compose file will be running at any one time
• The bridge network should be set manually by the user (perhaps override default network) and fixed.

These two will allow the deployment of single container instances e.g. the users controllers. This should wrap up a docker run --network=<our_default> -it --rm ... call by default. e.g. something like

starling deploy myrepo/my_controller
# or to add explicit docker run arguments
starling deploy myrepo/my_controller --run_args -itd --name my_controller

if a container is given with no -f flag, can treat as running a particular container.

In the future this can also service as the dynamic deployment of a container if a kubecluster is available.