You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In my case I override the db container to expose the postgres port on localhost in docker-compose.override.yml. Every time I run a command from divio-cli that uses the db container, it shuts it down and restarts it without the exposed port.
The default behaviour of
docker-compose
is to override anything in the defaultdocker-compose.yml
file with the values fromdocker-compose.override.yml
.https://docs.docker.com/compose/extends/#/understanding-multiple-compose-files
divio
cli seems to ignore the override file.In my case I override the db container to expose the postgres port on localhost in
docker-compose.override.yml
. Every time I run a command from divio-cli that uses the db container, it shuts it down and restarts it without the exposed port.example
docker-compose.yml
:example
docker-compose.override.yml
:The text was updated successfully, but these errors were encountered: