consider reduction of storage footprint and omitting docker dependency

[tobocop2]

Using up to 3 gigs of space with all bridges and element enabled for web is pretty ridiculous. Docker was used here because it enables very simple orchestration and it's portable, but a big downside is the space footprint.

A possible strategy could be doing orchestration entirely in go, and then the executable can manage the bridges directly from executables / scripts. This would remove the docker image size footprint completely but it is a lot of work. This is why docker is currently being used for orchestration. It's just too simple and it works and doesn't involve pulling platform dependent library code and executables.