Prisma not reading .env file

[MalekkJam]

Question

Hello, I am using Prisma 7.1.0 and after initilizing it i do the npx prisma db pull but i get the error in the photo

also i am using docker for postgres and adminer.
From what I saw I think the Prisma is not reading my .env file.
Here is the .env content : DATABASE_URL=postgresql://festivalapp:festivalapp@localhost:5432/festivalapp
docker-compose.dev.yml

How to reproduce (optional)

Expected behavior (optional)

No response

Information about Prisma Schema, Client Queries and Environment (optional)

// This is your Prisma schema file,
// learn more about it in the docs: https://pris.ly/d/prisma-schema

// Looking for ways to speed up your queries, or scale easily with your serverless or edge functions?
// Try Prisma Accelerate: https://pris.ly/cli/accelerate-init

generator client {
  provider = "prisma-client"
  output   = "../generated/prisma"
}

datasource db {
  provider = "postgresql"
}

// Add any relevant Prisma Client queries here

• OS: Windows

• Database: PostgreSQL

• Node.js version: V 22.19.0

• Run prisma -v to see your Prisma version and paste it

[sumyuck]

even though your .env is correct, the schema isn’t actually using it.

you need to point the datasource to DATABASE_URL:

datasource db {
  provider = "postgresql"
  url      = env("DATABASE_URL")
}

one more thing to watch out for with docker networking:

• if you’re running npx prisma db pull inside a docker container, localhost refers to that container, not the postgres container. in that case you should use the service name from your docker-compose.dev.yml, e.g.:

DATABASE_URL="postgresql://festivalapp:festivalapp@postgres:5432/festivalapp"
#                                      ^ this should be the postgres service name

• if you’re running the command directly on windows (not inside docker), then localhost is fine as long as you’ve published the port in compose, e.g. 5432:5432.

[nurul3101]

Is this resolved now?

[MalekkJam]

Thank you all for your answers, in fact I redowloaded Prisma so it started reading the .env however the P1000 error persisted. What I did then was a modification inside windows following the steps mentionned in this article. And it worked !

https://sweabhishek.medium.com/error-p1000-authentication-failed-against-database-server-the-provided-database-credentials-3793c85f8a77