Dev server won't start because of docker-compose.override.yml
In our docker-compose.override.yml file we mount a file in the nginx container. The dev deployment has no nginx anymore, so that leads to trouble:
tutor dev runserver cms
The cms service will be available at http://studio.totem.local:8001
docker-compose -f /datadisk/maarten/.local/share/tutor/env/local/docker-compose.yml -f /datadisk/maarten/.local/share/tutor/env/local/docker-compose.override.yml -f /datadisk/maarten/.local/share/tutor/env/dev/docker-compose.yml -f /datadisk/maarten/.local/share/tutor/env/dev/docker-compose.override.yml --project-name tutor_dev run --rm --service-ports cms
ERROR: The Compose file is invalid because:
Service nginx has neither an image nor a build context specified. At least one must be provided.
Error: Command failed with status 1: docker-compose -f /datadisk/maarten/.local/share/tutor/env/local/docker-compose.yml -f /datadisk/maarten/.local/share/tutor/env/local/docker-compose.override.yml -f /datadisk/maarten/.local/share/tutor/env/dev/docker-compose.yml -f /datadisk/maarten/.local/share/tutor/env/dev/docker-compose.override.yml --project-name tutor_dev run --rm --service-ports cms
Possible solutions:
- Move the proxy (learn.totem-project.org/js-components -> totem-project.org/js-components) from nginx to caddy. Caddy might not need this volume mount, or not have this problem
- Find a way to only use the override file in production deployments