i setup a simple docker compose file for just a prisma2 proj

Question

i setup a simple docker compose file for just a prisma2 project when i run it in the logs I get ```Error prisma client did not initialize yet Please run prisma generate and try to import it again ``` when i run `dk exec lt c name gt npx prisma generate` it says it s ready to use then I attempt to `dk exec lt c name gt npx prisma introspect` and I get ``` `Can t reach database server at `postgres` `5432``` I can confirm the db is working and that without docker the introspection works ive a volume setup which connects the docker container app folder and the local one when I change the `prisma env` url string to something else and `cat` to ensure it has changed it works but when I run `introspect` in the container again it says that it cannot connect with the default `5432` port even though I changed it

janpio · Answer

Is this the full output you get from `introspect`

janpio · Answer

What is you db connection string

janpio · Answer

inside docker

Max · Answer

```DATABASE URL= <postgresql user localhost 5432 db> docker exec lt c name gt npx prisma introspect Environment variables loaded from prisma env Introspecting based on datasource defined in prisma schema prisma Error P1001 Can t reach database server at `postgres` `5432` Please make sure your database server is running at `postgres` `5432` ```

Max · Answer

I am able to connect to the postgres db through tableplus as well as the same project when running locally without docker

Max · Answer

postgres is dockerized too

Max · Answer

it makes no sense to me that running `introspect` in the container after changing the port in `prisma env` results in the same error with the same port even though it s changed which leads me to believe it may be prisma s fault

janpio · Answer

That part was used quite a lot of times already so I would be surprised slightly smiling face

janpio · Answer

Give me a min to check sth

janpio · Answer

Hm the Postgres error message indeed only includes the host and port not the full connection string

janpio · Answer

But editing the port also changes it in my error message

Max · Answer

it does not for me let me try once again to make sure

Max · Answer

``` dkex back cat prisma env DATABASE URL= <postgresql user secret localhost 2000 db> dkex back npx prisma introspect Can t reach database server at `postgres` `5432````

Max · Answer

not quite sure why im getting the initial error on first start of the containers too in my op

janpio · Answer

Is that the full output

janpio · Answer

There should be more like in the snippet above

Max · Answer

it is the same as above

Max · Answer

1 1

janpio · Answer

Ok so you copied a modified version here

janpio · Answer

Strange as if it reads the file directly in the command there is really no way how it could get the wrong information really

janpio · Answer

Can you check if `DATABASE URL` is set manually somehow maybe not that it should influence that

Max · Answer

sweat smile

Max · Answer

I had an environment variable in my docker compose file with a wrong password

Max · Answer

`DATABASE URL` it was taking it from there

janpio · Answer

Ha

janpio · Answer

rocket

Max · Answer

thank you so much for the help and im sorry for wasting ur time lmao ur a gem

janpio · Answer

Still strange that it was using that one although it said it used the file

Max · Answer

yea i was a bit naive to not question that

janpio · Answer

I would have expected the local file to overwrite the value set in the environment

Max · Answer

same

Max · Answer

i dont want to say how long I spent trying to figure this out

Max · Answer

sweat smile

Max · Answer

by the way to clarify something related if I set the db url in the ` env` which is in the root of my project managed by `dotenv` dep which would take precedence could I omit the `prisma env` file entirely in that scenario

janpio · Answer

But I can confirm that behavior and will open a bug issue

Max · Answer

much appreciated

janpio · Answer

Yes `prisma env` is just a default location we read by convention

janpio · Answer

You can create the env var whatever way you want

Max · Answer

thumbsup

janpio · Answer

Max · Answer

I think a bit more verbose errors would be quite nice when unable to connect to the database because I just ran into the same exact issue however this time I m quite certain that the env var is not being overwritten by anything as it recognizes the changes

Max · Answer

and yet I am getting the same exact error despite both containers being on the same network can connect to each other url string is correct etc and its likely something simple im missing again hah

janpio · Answer

Hm but what could a better error message be

Richard Ward · Answer

< Max> what you can do for the ` env` file is use your general one in your root put the DB connection string in there and then ```cd prisma ln s env``` That will create a link `prisma env` which links to your project ` env`

Max · Answer

< Richard Ward> good thinking thanks