Example .yml for docker install does not work with database in same docker network

[lamachine]

Describe the issue
I cannot figure out a setup that lets it connect to postgres
-127.0.0.1 (Localhost) inside a container means "THIS container".
-Hatchet tries to connect to 127.0.0.1:5432, it's looking for a database inside itself.
-It must connect to postgres (the container name) on the shared network.

It just keeps circling the drain, either no logs on api and engine constantly restarting, or both constantly restarting. Cookie errors or can't read keyset or.... If I get both running stably, then I get a 502 error on the dashboard.

Environment

• ghcr.io/hatchet-dev/hatchet/hatchet-engine:latest
  -ghcr.io/hatchet-dev/hatchet/hatchet-api:latest
  Latest version of docker desktop on Win.
  Supabase running in docker container

Expected behavior
Expected to follow yml config and connect. This is all before I have even tried to connect to the service.

Hatchet API_Engine Startup Failures.md

Code to Reproduce, Logs, or Screenshots
Include a minimal code snippet that reproduces the issue, error logs around the event, or screenshots, if applicable.

Additional context
Anything else that might help us understand or reproduce the problem — e.g. specific page URL, logged-in vs logged-out, related docs or workflows.

[gregfurman]

Hey @lamachine. I'm looking to improve some of the developer docs so am curious about which example YAML you're referring to. I assume you've already seen https://docs.hatchet.run/self-hosting/docker-compose 👀

-Hatchet tries to connect to 127.0.0.1:5432, it's looking for a database inside itself.

I assume you're using docker compose? That means you can directly reference the name of your container i.e

services:
  postgres:
    ports:
      - "5435:5432"
  hatchet-engine:
    image: ghcr.io/hatchet-dev/hatchet/hatchet-engine:latest
    environment:
      # notice the postgres:5432 is used as the address
      DATABASE_URL: "postgres://hatchet:hatchet@postgres:5432/hatchet"

Otherwise, can you share a snippet of your compose YAML, or commands for how you're starting up your containers?

[lamachine]

You DEFINATLY should be able to. The example one is where i started yesterday.

`
version: "3.8"

services:
# RabbitMQ: Explicit User/Pass and Healthcheck
rabbitmq:
image: "rabbitmq:3-management"
hostname: "rabbitmq"
ports:
- "5673:5672"
- "15673:15672"
environment:
RABBITMQ_DEFAULT_USER: ${RABBITMQ_USER:-hatchet}
RABBITMQ_DEFAULT_PASS: ${RABBITMQ_PASS:-hatchet_secret}
healthcheck:
test:
interval: 10s
timeout: 10s
retries: 5
networks:
- hatchet_network

# Migration Service: Handles DDL
# Connects via Session Mode (Port 5432) with SSL Disabled
migration:
image: ghcr.io/hatchet-dev/hatchet/hatchet-migrate:latest
environment:
DATABASE_URL: "postgresql://${POSTGRES_USER}:${POSTGRES_PASS}@${POSTGRES_HOST}:5432/${POSTGRES_DB}?sslmode=disable"
networks:
- hatchet_network

# Setup Config: Initializes System State
setup-config:
image: ghcr.io/hatchet-dev/hatchet/hatchet-admin:latest
command: /hatchet/hatchet-admin quickstart --skip certs --generated-config-dir /hatchet/config --overwrite=false
environment:
DATABASE_URL: "postgresql://${POSTGRES_USER}:${POSTGRES_PASS}@${POSTGRES_HOST}:5432/${POSTGRES_DB}?sslmode=disable"
SERVER_ENCRYPTION_MASTER_KEYSET: ${SERVER_ENCRYPTION_MASTER_KEYSET}
SERVER_ENCRYPTION_JWT_PUBLIC_KEYSET: ${SERVER_ENCRYPTION_JWT_PUBLIC_KEYSET}
SERVER_ENCRYPTION_JWT_PRIVATE_KEYSET: ${SERVER_ENCRYPTION_JWT_PRIVATE_KEYSET}
SERVER_AUTH_COOKIE_SECRETS: ${SERVER_AUTH_COOKIE_SECRETS}
SERVER_MSGQUEUE_RABBITMQ_URL: "amqp://${RABBITMQ_USER:-hatchet}:${RABBITMQ_PASS:-hatchet_secret}@rabbitmq:5672/"
depends_on:
rabbitmq:
condition: service_healthy
migration:
condition: service_completed_successfully
volumes:
- hatchet_config:/hatchet/config
networks:
- hatchet_network

# Hatchet Engine: Core Logic
hatchet-engine:
image: ghcr.io/hatchet-dev/hatchet/hatchet-engine:latest
command: /hatchet/hatchet-engine --config /hatchet/config
restart: on-failure
ports:
- "7077:7070" # Expose gRPC for external workers
environment:
DATABASE_URL: "postgresql://${POSTGRES_USER}:${POSTGRES_PASS}@${POSTGRES_HOST}:5432/${POSTGRES_DB}?sslmode=disable"
SERVER_ENCRYPTION_MASTER_KEYSET: ${SERVER_ENCRYPTION_MASTER_KEYSET}
SERVER_ENCRYPTION_JWT_PUBLIC_KEYSET: ${SERVER_ENCRYPTION_JWT_PUBLIC_KEYSET}
SERVER_ENCRYPTION_JWT_PRIVATE_KEYSET: ${SERVER_ENCRYPTION_JWT_PRIVATE_KEYSET}
SERVER_AUTH_COOKIE_SECRETS: ${SERVER_AUTH_COOKIE_SECRETS}
SERVER_MSGQUEUE_RABBITMQ_URL: "amqp://${RABBITMQ_USER:-hatchet}:${RABBITMQ_PASS:-hatchet_secret}@rabbitmq:5672/"

  \# Networking Criticals:  
  \# Binds to 0.0.0.0 to accept connections from outside the container  
  SERVER\_GRPC\_BIND\_ADDRESS: "0.0.0.0"  
  \# Advertises the internal docker DNS name for other containers  
  SERVER\_GRPC\_BROADCAST\_ADDRESS: "hatchet-engine:7070"  
  SERVER\_GRPC\_INSECURE: "true"  
depends\_on:  
  setup-config:  
    condition: service\_completed\_successfully  
  rabbitmq:  
    condition: service\_healthy  
volumes:  
  \- hatchet\_config:/hatchet/config  
networks:  
  \- hatchet\_network

# Dashboard & API Proxy
hatchet-dashboard:
image: ghcr.io/hatchet-dev/hatchet/hatchet-dashboard:latest
command: sh./entrypoint.sh --config /hatchet/config
ports:
- "8080:80"
restart: on-failure
environment:
DATABASE_URL: "postgresql://${POSTGRES_USER}:${POSTGRES_PASS}@${POSTGRES_HOST}:5432/${POSTGRES_DB}?sslmode=disable"
SERVER_URL: "http://localhost:8080"
SERVER_ENCRYPTION_MASTER_KEYSET: ${SERVER_ENCRYPTION_MASTER_KEYSET}
SERVER_ENCRYPTION_JWT_PUBLIC_KEYSET: ${SERVER_ENCRYPTION_JWT_PUBLIC_KEYSET}
SERVER_ENCRYPTION_JWT_PRIVATE_KEYSET: ${SERVER_ENCRYPTION_JWT_PRIVATE_KEYSET}
SERVER_AUTH_COOKIE_SECRETS: ${SERVER_AUTH_COOKIE_SECRETS}
SERVER_MSGQUEUE_RABBITMQ_URL: "amqp://${RABBITMQ_USER:-hatchet}:${RABBITMQ_PASS:-hatchet_secret}@rabbitmq:5672/"
SERVER_AUTH_COOKIE_INSECURE: "true" # Required for non-HTTPS localhost access
SERVER_AUTH_COOKIE_DOMAIN: "localhost"
depends_on:
hatchet-engine:
condition: service_started
volumes:
- hatchet_config:/hatchet/config
networks:
- hatchet_network

volumes:
hatchet_config:

networks:
hatchet_network:
driver: bridge
`