3 months ago
As stated in title.
I've tried bitnami/pgbouncer:latest and edoburu/pgbouncer and none actually deploy. there are no errors just continuous supposed deployment for over 10 mins with no logs.
1 Replies
3 months ago
This isn’t a PgBouncer image issue, it’s a Railway runtime/health-check mismatch.
PgBouncer images don’t expose an HTTP port or emit logs by default, so Railway keeps waiting for the service to become “healthy” and sits forever at Creating containers.
Fix:
Explicitly set a TCP port PgBouncer listens on (e.g.
LISTEN_PORT=3000)Disable HTTP health checks or switch the service to TCP mode
Or add a dummy
PORTenv + command so Railway sees the container as alive
Railway assumes every service is a web app unless told otherwise which PgBouncer isn’t one.