password authentication failed for user "postgres" with docker-compose up on EC2

Question

On EC2 linux server create by docker-machine, when I launch docker postgres:10.6 by docker-compose up, I have these loop errors :

FATAL:  password authentication failed for user "postgres"
DETAIL:  Password does not match for user "postgres".
Connection matched pg_hba.conf line 95: "host all all all md5"

I don't have these errors if I start container manually => docker run -e POSTGRES_PASSWORD=myPassword postgres:10.6

I don't have these errors in my local docker.

My docker-compose :

db:
  container_name: postgres
  image: postgres:10.6
  restart: always
  environment:
    POSTGRES_PASSWORD: myPassword
  ports:
    - "5432:5432"

Does anyone know how to fix this?

Akshay Shah · Accepted Answer · 2019-04-13 17:58:29Z

20

It might be because the volume (or bind mount directory) being already initialized after your first start. The postgres user, and database creation only happens on the first start (ie, /var/lib/postgresql/data must not already contain database files). Try to run:

docker-compose rm -fv postgres to delete any containers or volumes (in particular).
docker-compose up -d to start your container.

answered Apr 13, 2019 at 17:58

Akshay Shah

7344 silver badges12 bronze badges

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

4 Comments

O.Badr Over a year ago

Use docker-compose rm -sfv postgres instead, if you are not sure whether the container is running or not

Joshua Swain Over a year ago

I had to run docker volume ls to find the name of the volume, and then docker volume rm <volume_name>. Then I could reinitialize the postgres volume

Ulug'bek Over a year ago

thanks a lot. It helps. In my case, when I create docker image at the first time I run with sudo. I advise others also don't repeat my mistake

Digao Over a year ago

I had to make sure no app was still referencing the db with the old credentials..

Edouard · Accepted Answer · 2019-04-14 10:09:41Z

0

Sorry for that I have the answer to my question, it's not a bug I just have something that tries to connect permanently to postgres (through port 5432 which is open) ...

After search, I think it's an attempt at hacking because incoming connections never come from the same IP

connection received: host=45.120.120.149.81 port=47118
connection received: host=210.4.125.252 port=44774
connection received: host=82.223.55.254 port=36320

etc....

edited Apr 14, 2019 at 10:09

answered Apr 14, 2019 at 9:43

Edouard

1311 gold badge1 silver badge4 bronze badges

1 Comment

Brandon Petty Over a year ago

If you previously had PgAdmin setup with Postgres w/o a password, and then tried setting one via POSTGRES_PASSWORD, you will also see repeating login failures just like this.

Collectives™ on Stack Overflow

password authentication failed for user "postgres" with docker-compose up on EC2

2 Answers 2

4 Comments

1 Comment

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

2 Answers 2

4 Comments

1 Comment

Your Answer

Sign up or log in

Post as a guest