Version postgres:9.4 doesn't create role/password

[pandeiro]

Setting POSTGRES_USER and POSTGRES_PASSWORD on the 9.4 tag doesn't create the role and password for me. (Previous versions work.)

[yosifkit]

That is a bit strange, I'm not having any problems here and I just did a docker pull -a to be sure. I would say docker version or storage driver could be a problem, but you say the other versions work fine and the files we use in each are almost identical (the entrypoint setting the user/password is identical).

[pandeiro]

I'm still having the problem. Just to clarify, the expected behavior is that setting those variables will create the role and password and restrict login to those credentials. When I pass the variables and then try to login to the container, Postgres says the role doesn't exist.

Edit: It's hard to put a minimal case because a client like psql must be present on the host machine to test. But if all else fails to detect this, I can try something.

In case this helps, docker version:

Docker version 1.4.0, build 4595d4f

and docker info:

Containers: 63
Images: 566
Storage Driver: devicemapper
 Pool Name: docker-8:3-9965829-pool
 Pool Blocksize: 65.54 kB
 Data file: /home/user/data/docker/devicemapper/devicemapper/data
 Metadata file: /home/user/data/docker/devicemapper/devicemapper/metadata
 Data Space Used: 13.72 GB
 Data Space Total: 107.4 GB
 Metadata Space Used: 25.68 MB
 Metadata Space Total: 2.147 GB
 Library Version: 1.02.92 (2014-11-28)
Execution Driver: native-0.2
Kernel Version: 3.17.6-1-ARCH
Operating System: Arch Linux
CPUs: 4
Total Memory: 7.716 GiB
Name: userhost
ID: CWFN:OTRR:L5GE:VFDJ:DJ26:XQSD:KQSP:ZC6V:LHJU:CDFS:B2ZL:YZU6

[yosifkit]

Yes it creates the user specified as a superuser with the password and creates a database for them. Here is how I'm testing it:

$ docker run -it --rm --name pg1 -e POSTGRES_PASSWORD=12345 -e POSTGRES_USER=bob postgres:9.4

$ docker run -it --link pg1:postgres --rm postgres:9.4 sh -c 'exec psql -h "$POSTGRES_PORT_5432_TCP_ADDR" -p "$POSTGRES_PORT_5432_TCP_PORT" -U bob'

[pandeiro]

I just did that and get psql: FATAL: role "bob" does not exist.

Edit: I tried on another machine and it does work. Clearly something local here -- sorry. Feel free to close this.

[ferrouswheel]

I get the same issue

$ docker version
Client version: 1.3.0
Client API version: 1.15
Go version (client): go1.3.3
Git commit (client): c78088f
OS/Arch (client): darwin/amd64
Server version: 1.3.0
Server API version: 1.15
Go version (server): go1.3.3
Git commit (server): c78088f

Not sure how the logic of changing role/password could be version dependent. But happy to help to try and debug why some of us get this issue.

I've tried setting POSTGRES_USER/POSTGRES_PASSWORD on a container with an existing db volume, and with a blank data volume in case the user/password is only set up the first time things get initialised (the documentation is unclear if setting user/password will be respected on a container with an existing data volume).

[ferrouswheel]

Tracked this down to the docker-entrypoint.sh in my pulled image being different to the one in this repo:

#!/bin/bash
set -e

if [ "$1" = 'postgres' ]; then
    chown -R postgres "$PGDATA"

    if [ -z "$(ls -A "$PGDATA")" ]; then
        gosu postgres initdb

        sed -ri "s/^#(listen_addresses\s*=\s*)\S+/\1'*'/" "$PGDATA"/postgresql.conf

        { echo; echo 'host all all 0.0.0.0/0 trust'; } >> "$PGDATA"/pg_hba.conf

        if [ -d /docker-entrypoint-initdb.d ]; then
            for f in /docker-entrypoint-initdb.d/*.sh; do
                [ -f "$f" ] && . "$f"
            done
        fi
    fi

    exec gosu postgres "$@"
fi

exec "$@"

And turns out I was using the version tagged 9.3 in my config.

[liamdawson]

I had this issue, then realised I had another postgres working on my machine. Oops. Make sure you check that!

[Alexis-benoist]

I'm having the same issue.

@liamdawson: for you the problem was that postgres was running on your machine or installed?

How did you solve this issue?

[liamdawson]

@Alexis-benoist I had postgres actually running on my host, so it took precedence over the version run in Docker.

[stabenfeldt]

This is how you start the docker postgres image and access:

$ docker run -it --rm --name pg1 -p 5432:5432 -e POSTGRES_PASSWORD=12345 -e POSTGRES_USER=bob postgres:9.4

$ psql -h dockerhost  -U bob

The incoming ports was not defined in @yosifkit's example. :-)
-p 5432:5432

[tibo]

I've got the same issue using docker-compose
the POSTGRES_USER environment variable doesn't seems to create the user properly?

[yosifkit]

@tibo, with docker-compose, it tries to preserve volumes between runs; since the user is only created on a new database, you probably need to docker-compose rm -v database to delete the container and associated volume.

[tibo]

@yosifkit good call. setting POSTGRES_USER at the creation of the container works.
Thanks!

[servomac]

I have the same problem with docker-compose and an specified POSTGRES_USER:

 postgres:
     image: postgres:9.4.1
     environment:
         - POSTGRES_PASSWORD=supersecret
         - POSTGRES_USER=username
         - POSTGRES_DB=dbname

Results in

$ psql -U username
psql: FATAL:  role "username" does not exist

It works with the 9.5 tag.

[jmerkow]

I have this problem with 9.5 tag. I am running it from OS X (docker-machine with virtual box drivers). The same files do no have issues running from a ubuntu 14.04 machine.
Perhaps, this has something to do with the host os for docker?