This could be the consequence of you trying to start those heavy jobs once every it seems that’s set as a disk bandwidth limit in your docker container.
Current best practice is to start the node & background jobs as a systemd service instead, so that the OS will detect when they have stopped and restart them automatically, under all conditions when the process fails, system reboots, etc.; e.g. the systemd service scripts here (modify to suit your system):
topologyUpdater.sh is not a background service, just a run-through script, so it’s fine as you’ve listed it… but other Cardano utilities that run continuously have been made to run more efficiently as services, e.g.: