In the attempt to understand the issues I got with starting up SDC, Examples are taken from SDC, the issue itself is of general nature.

I discovered that some scripts "assume" certain steps to be completed in a hard coded. Examples are the delay time between container starts in /data/scripts/docker_run.sh in the VM as well as /root/chef-solo/cookbooks/sdc-normatives/files/default/check_Backend_Health.py in the backend docker image. These times could be too optimistic for some lab-style setups (like mine). In addition, if a scripts times out, there is no action take to deal with the time out.

Other example is that sdc-BE calls sdc-cs before sdc-cs has

As an alternative, a condition needs to be defined for a component A to recognized when a component B, which A is depended on, is ready to serve.