1 point
*
Simpler to keep everything in one compose file if you can, under a test service that doesn’t build unless explicitly named
Un-weird that env var and use the normal, boring feature of defining environment under your test service
1 point
The variable is already in the environment, it just doesn’t have a default because it’s required for each container
1 point
You can reference envs from the host in docker compose, so code it in instead of manually passing tribal knowledge in: https://stackoverflow.com/a/73826410
1 point
*
