I have a docker-compose override file to use for running tests on containers. I want to start my node server with a different command - nyc node server.js. I have a docker-compose.coverage.yml file that overrides the normal compose file like so:
node:
command: nyc node server.js
However, it never seems to override the command when I do docker-compose -f docker-compose.yml -f docker-compose.coverage.yml start node. When I use docker-compose run it overrides the command, but the service exits. Does anyone know why it wouldn't be overriding the command using start?
docker-compose start will start an existing, stopped container. An existing container will already have the command baked in, and you can't change it.
What you want to do is use docker-compose up. This will look for changes to docker-compose.yml, and if there's anything to change, it will recreate the container with the new options, then start or restart it.
So you want something like this:
docker-compose -f docker-compose.yml -f docker-compose.coverage.yml up -d node