M1 Related! - Prisma: Can't reach database server at `database`:`5432`

Question

Since I have moved to the new Apple Silicon architecture my docker setup with nextjs and postgres is not working anymore. The database inside the docker cannot be found by the nextjs server where I am using prisma.

The prisma client can't reach the postgres database on port 5432.

Can't reach database server at test-postgres:5432

The migration also does not work and returns the same error above.

docker-compose run --publish 5555:5555 next npx prisma migrate dev

docker-compose.yml

postgres:
    container_name: 'test-postgres'
    restart: unless-stopped
    image: 'postgres:13'
    ports:
      - '15432:5432'
    volumes:
      - 'pgdata:/var/lib/postgresql/data/'
    environment:
      POSTGRES_PASSWORD: postgres

.env

DATABASE_URL="postgres://postgres:postgres@localhost:15432/postgres"

I have also added the arm binary target to the schema.prisma schema.prisma


generator client {
  provider        = "prisma-client-js"
  binaryTargets   = ["native", "debian-openssl-1.1.x", "linux-arm-openssl-1.1.x", "linux-musl"]
  previewFeatures = ["orderByRelation", "selectRelationCount"]
}

The postgres container is actually running and I can see it through the Docker Desktop Dashboard. One thing I have noticed inside the postgres container was this ERROR:

2021-07-21 12:52:58.927 UTC [76] ERROR:  relation "_prisma_migrations" does not exist at character 126

Have someone experienced it before and found a solution for it?

[EDIT]

How to reproduce

clone repo, follow README.md and see expected behaviour on a M1 Apple Silicon Machine: https://github.com/baristikir/prisma-postgres-M1

score 70 · Accepted Answer · answered Jul 23 '21 at 07:06

70

Adding ?connect_timeout=300 to the connection string of the database did the trick.

DATABASE_URL="postgres://postgres:postgres@localhost:15432/postgres?connect_timeout=300"

answered Jul 23 '21 at 07:06

brstkr

1,423
3
18
28

2

nice, worked for me – Bjørson Bjørson Jan 29 '22 at 18:39
1

Got this error for two weeks now, thank you so much! – Lukas Marschall May 01 '22 at 17:04
2

It definitely does the trick. No idea why though. – Arslan Khan Jul 20 '22 at 14:32
Dude, literally, I was looking for this like 4 hours or smth, thx – blazej Aug 15 '22 at 15:33
3

No way, how can this work? And it has 36 upvotes. How adding a connection timeout can solve the problem? Can you explain?? – Subash Shrestha Aug 21 '22 at 14:39
It works! Without knowing what's the cause. Thank you. – Muhaimin Taib Oct 12 '22 at 03:10
that's my champion – Sebastien H. Dec 07 '22 at 16:41
It doesn't work with my mariadb database (I'm using ssl). Fails instantly on my device when I add the option and on vercel it always times out instantly, too. However on my device it works if I don't specify anything. – france1 Jan 16 '23 at 19:55
We were setting up our backend with prisma in 8 kubernetes pods Since we made so many connections at one go, it was timing out, and only ~4 pods were able to connect at one go. In our case, this param makes a lot sense, since it increased the timeout for connection from 30s to 5mins, and it worked!!! – heethjain21 Feb 14 '23 at 15:34
All hail the saviour. Hallelujah – Allen Jun 01 '23 at 07:19

abel-mak · Answer 2 · 2022-09-16T11:20:13.467

8

I had this issue on m1 mac mini, the solution was changing the version of node from v16.16.0(image node:16) to v17.9.1(node:17), we tried on node:18 it works also. I changed Dockerfile from

FROM node:16

to

FROM node:17

edited Sep 16 '22 at 11:20

answered Jul 22 '22 at 21:07

abel-mak

121
1
4

17 alphine version isn't working. must be 17 version – magentaqin May 29 '23 at 14:16
I spent so much time trying to figure this out. Im on an m2 mac book air, this fixed my issue for good. More people should be able to find this when they need it. thank you so much for this comment. – RashadArbab Aug 31 '23 at 19:08

score 1 · Answer 3 · answered Aug 19 '22 at 16:00

1

I was using 16.17.0 version of Node. Just switched back to 16.13.2 and the issue is solved.

answered Aug 19 '22 at 16:00

William Philppe

61
5

score 0 · Answer 4 · edited Nov 14 '22 at 16:17

0

I got the same issue and I added ?connect_timeout=300 and it worked. I realized it's taking some time, before connecting to the database especially when it's from a cloud provider, therefore the error.

edited Nov 14 '22 at 16:17

ASR4

545
1
8
24

answered Nov 09 '22 at 11:03

Freedisch

124
1
9

This does not provide an answer to the question. Once you have sufficient [reputation](https://stackoverflow.com/help/whats-reputation) you will be able to [comment on any post](https://stackoverflow.com/help/privileges/comment); instead, [provide answers that don't require clarification from the asker](https://meta.stackexchange.com/questions/214173/why-do-i-need-50-reputation-to-comment-what-can-i-do-instead). - [From Review](/review/late-answers/33141226) – Josua Marcel C Nov 15 '22 at 18:33

score 0 · Answer 5 · answered Dec 27 '22 at 03:30

0

With me I just change the database URL:

DATABASE_URL="postgresql://root:root@<My IP>:5432/<MY DB Name>"

And it works fine.

answered Dec 27 '22 at 03:30

Bob Nguyen

11
1

What is "My IP"? Your public local IP or 127:0.0.1 ? – Leafyshark Jan 31 '23 at 15:56
It's "Your public local IP" hope to help u. – Bob Nguyen Feb 17 '23 at 04:34

M1 Related! - Prisma: Can't reach database server at `database`:`5432`

How to reproduce

5 Answers5

Linked