Issue using the new "docker compose" command with Vanilla Docker
I upgraded Docker to the latest version and attempted to bring up my stack with docker-compose. The command brought everything up, but not before informing me I should try using docker compose (note the space instead of a dash), next time. I tried it and...my local site didn't work, anymore. Specifically, my database container stopped coming up.
It turns out docker compose (a command of the docker CLI application) is mostly a drop-in replacement for docker-compose (a standalone CLI application), with at least one key exception: it does not automatically load docker-compose.override.yml. Vanilla's Docker setup comes with a docker-compose.override.yml by default, so just running docker compose up in the project won't cut it in most cases. As of now, you'll need to specify both your basic config(s) and the "overrides", individually. For example:
docker compose --file docker-compose.yml --file docker-compose.override.yml up
You'd also need to use a symmetrical down command, but that's really it. I don't believe docker-compose is going away anytime soon, so there's no rush to hop on the docker compose train, but it likely will at some point. When it does, there's a good chance this will still be the behavior of docker compose (based on the last response to docker/compose-cli#1546)