Local development login fails because backend cannot resolve db in Docker Compose

[Zhey-on]

Summary

In local development, login with the seeded demo user can fail even with correct credentials because backend DB hostname resolution breaks inside Docker.

Steps to reproduce

1. Start local dev stack with docker compose up -d.
2. Try to login from frontend using:
   • email: demo_company_admin@example.com
   • password: 123123
3. Or call backend directly:
   • POST /api/auth/login

Expected behavior

Login returns a JWT token.

Actual behavior

Login fails with server-side errors similar to:

SQLSTATE[HY000] [2002] php_network_getaddresses: getaddrinfo for db failed: Temporary failure in name resolution

Root cause

In this environment, service/container DNS aliases (db, and in some cases redis) were not consistently resolvable from backend containers.

Proposed fix

Add explicit network aliases on the default compose network:

• mysql: aliases db, mysql
• redis: alias redis

Apply the same fix in:

• docker-compose.yml
• docker-compose-prod.yml
• docker-compose-dockerhub.yml

Then recreate containers with docker compose up -d --force-recreate.

[dmohns]

I'm having a hard time to reproduce this issue. Could you provide information about your setup and runtimes?

1. Environment

• OS (e.g. macOS, Linux, Windows + version)
• CPU architecture (Intel/AMD/ARM)
• Are you using Docker Desktop or native Docker or alternatives like Orbstack?

2. Docker versions

docker version 
docker compose version