docker compose ignoring env vars when creating the container for postgres

Question

I always get role x does not exist which means the db was created with the default username and my env vars was ignored, any idea whats going on here?

Docker-compose.yml

version: '3.1'

services:
  PostgreSQL:
    container_name: db-name
    image: postgres:12
    restart: always
    environment:
      POSTGRES_PASSWORD: ${PG_PASSWORD}
      POSTGRES_USER: ${PG_USERNAME}
      POSTGRES_DB: ${PG_DB_NAME}
    volumes:
      - ./postgres-data:/var/lib/postgresql/data
    ports:
      - 5432:5432

When I look in kitematic I see the correct env variables and values, but nothing is taking in consideration by the db

Are you sure the database was not already created? It will only be created and initialized if the files in /var/lib/postgresql/data from your mounted volume are empty. — Thilo
– Thilo, Commented Feb 8, 2020 at 13:27
I up with forece recreate docker-compose up --force-recreate I don't think the db will persist — JSK
– JSK, Commented Feb 8, 2020 at 13:53
I tried docker-compose down --remove-orphans --volumes still same problem — JSK
– JSK, Commented Feb 8, 2020 at 13:55

peterzinho16 · Accepted Answer · 2020-02-08 13:34:21Z

3

Try doing docker-compose down to remove the container and do again docker-compose up, you can get more help from this link

answered Feb 8, 2020 at 13:34

peterzinho16

9891 gold badge16 silver badges19 bronze badges

Sign up to request clarification or add additional context in comments.

1 Comment

JSK Over a year ago

thank you for the link I found an answer there, I had the manually delete the ./postgres-data created by docker compose

Collectives™ on Stack Overflow

docker compose ignoring env vars when creating the container for postgres

1 Answer 1

1 Comment

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

1 Comment

Your Answer

Sign up or log in

Post as a guest

Related