Unable to connect to the database error on all containers
After updating my stack to the latest, I'm starting to get this same error in all containers that are not the databases:
`
However, all the containers are on the same network, and the container databases are just fine, ready to accept connections. Did something in the way the containers reach the database have changed? I don't understand why they are trying to go through localhost rather than using the container name.
1 Reply
I fixed it by adding more env variables to the .env file, specifically those about the databases hostnames:
This should be considered a breaking change, because previously they were optional, but now they are mandatory, and without them the server will not start, and will fallback to localhost, which will only work on the development environment
However, nothing is stated on the changelog
Please consider mentioning this