fix: update docker-compose volume mount for PostgreSQL 18+ compatibility

[swalihkolakkadan]

What does this PR do?

Updates the volume mount path in packages/prisma/docker-compose.yml from /var/lib/postgresql/data to /var/lib/postgresql to fix compatibility with PostgreSQL 18+.

PG 18 changed its data directory layout to use /var/lib/postgresql/18/main instead of /var/lib/postgresql/data (see docker-library/postgres#1259). The old mount path causes the container to fail the healthcheck and yarn dx to error out.

• Fixes PostgreSQL container fails to start with postgres:18 due to incorrect volume mount path #28281

Visual Demo (For contributors especially)

Before (container crash loop):

@calcom/prisma:db-up: ✘ Container prisma-postgres-1 Error dependency postgres failed to start
@calcom/prisma:db-up: dependency failed to start: container prisma-postgres-1 is unhealthy

After (healthy container):

$ docker ps --filter "name=prisma"
NAMES               STATUS                    PORTS
prisma-postgres-1   Up 35 seconds (healthy)   0.0.0.0:5450->5432/tcp

Mandatory Tasks (DO NOT REMOVE)

• I have self-reviewed the code (A decent size PR without self-review might be rejected).
• I have updated the developer docs in /docs if this PR makes changes that would require a documentation change. N/A — one-line config fix, no docs needed.
• I confirm automated tests are in place that prove my fix is effective or that my feature works. N/A — docker-compose config change, verified manually by running yarn dx.

How should this be tested?

1. Run docker compose -f packages/prisma/docker-compose.yml down -v to clear any existing volumes
2. Run yarn dx
3. Confirm the postgres container starts healthy: docker ps --filter "name=prisma" should show status as healthy

No environment variables or test data needed — this only affects the local dev database setup.

Note: Existing users with volumes from older PG versions will need to run docker compose down -v once to clear the incompatible volume. This is a local dev database so no data is lost — yarn dx re-seeds everything.

[cubic-dev-ai]

No issues found across 1 file