Question

A network automation team runs a Docker Compose stack for their CI validation environment. The stack defines a 'postgres' service and a 'nautobot' service, where 'nautobot' has `depends_on: [postgres]`. Engineers report that 'nautobot' intermittently crashes on startup with database connection errors, even though 'postgres' is listed as a dependency. Reviewing the Compose file, they see 'postgres' has no `healthcheck` defined. Which change to the Compose file will most reliably prevent 'nautobot' from starting before the database is ready to accept connections?

Accepted Answer

Add a `healthcheck` to the 'postgres' service and change 'nautobot' to use `depends_on:` with `condition: service_healthy` for postgres.

Answer

Add `links: [postgres]` to the 'nautobot' service so Compose waits for postgres to be fully initialized before starting nautobot.

Answer

Move both services onto the same custom `network` so that Docker delays nautobot startup until postgres has an IP address.

Answer

Add a shared named `volume` between postgres and nautobot so nautobot reads the database ready state from the volume before starting.