I’ve often been able to alias drun='docker compose run --rm --build' and simplify down to:
drun test
Should be able to encode all those wayward args into docker-compose.yml or Dockerfile and only use vanilla docker commands – that’s the whole point of containerization
The env file is the weirdest part, the container itself has a required environment variable and if I don’t pass it in command line (only have it in the test compose file) the base compose fails because it has no port.
Most of the other commands are to merge the compose files so I can keep my base compose file clean!
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
I’ve often been able to
alias drun='docker compose run --rm --build'and simplify down to:Should be able to encode all those wayward args into
docker-compose.ymlorDockerfileand only use vanilla docker commands – that’s the whole point of containerizationThe env file is the weirdest part, the container itself has a required environment variable and if I don’t pass it in command line (only have it in the test compose file) the base compose fails because it has no port.
Most of the other commands are to merge the compose files so I can keep my base compose file clean!
Simpler to keep everything in one compose file if you can, under a
testservice that doesn’t build unless explicitly namedUn-weird that env var and use the normal, boring feature of defining
environmentunder yourtestserviceThe variable is already in the environment, it just doesn’t have a default because it’s required for each container
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