Describe the bug
Occasionally (e.g. for me, after a few tries), when spinning up the system with docker-compose up -d, I have a few services fall over due to a missing AM address from the environment. I'm assuming this is some sort of race condition where we spin up those services a little too quickly. If I start those services again it usually works.

To Reproduce
Steps to reproduce the behavior:

1. Follow README.md instructions to build master and get ready to spin it up.
2. Run something computationally heavy in the background like screen sharing in a google meet, another service, etc.
3. run docker-compose up -d and start integration tests
4. If it works, repeat 2. and 3. until it fails

I think I have seen this persist even when bringing again with the same volumes, but I cannot consistently reproduce it.

Expected behavior
System should consistently start up on the first try.

Error Messages
in the message_relayer:

Error: Must pass ADDRESS_MANAGER_ADDRESS
at main (/opt/optimism/packages/message-relayer/src/exec/run.ts:29:11)
at /opt/optimism/packages/message-relayer/exec/run-message-relayer.js:6:9
at Object.<anonymous> (/opt/optimism/packages/message-relayer/exec/run-message-relayer.js:7:3)
at Module._compile (internal/modules/cjs/loader.js:1063:30)
at Object.Module._extensions..js (internal/modules/cjs/loader.js:1092:10)
at Module.load (internal/modules/cjs/loader.js:928:32)
at Function.Module._load (internal/modules/cjs/loader.js:769:14)
at Function.executeUserEntryPoint [as runMain] (internal/modules/run_main.js:72:12)
at internal/main/run_main_module.js:17:47

in batch_submitter:

{"level":30,"time":1619130363690,"msg":"Starting batch submitter..."}
{"level":40,"time":1619130363690,"varName":"ADDRESS_MANAGER_ADDRESS","msg":"Missing environment variable"}

System Specs:

• OS: Mac 11.2.1
• Package Version (or commit hash): 1746244