sameersbn / sameersbn/docker-gitlab
psql: FATAL: password authentication failed for user "gitlab"
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 8.1k
- Forks
- 2.1k
- Avg merge
- 17h 47m
- Merged PRs (30d)
- 7
Description
Hello all,
i used default configuration but when i trying start gitlab container i get msg "psql: FATAL: password authentication failed for user "gitlab"
Initializing logdir...
Initializing datadir...
Installing configuration templates...
Configuring gitlab...
Configuring gitlab::database..........
Configuring gitlab::redis
Configuring gitlab::secrets...
Configuring gitlab::sidekiq...
Configuring gitlab::gitlab-workhorse...
Configuring gitlab::unicorn...
Configuring gitlab::timezone...
Configuring gitlab::rack_attack...
Configuring gitlab::ci...
Configuring gitlab::artifacts...
Configuring gitlab::lfs...
Configuring gitlab::project_features...
Configuring gitlab::oauth...
Configuring gitlab::ldap...
Configuring gitlab::backups...
Configuring gitlab::registry...
Configuring gitlab-shell...
Configuring nginx...
Configuring nginx::gitlab...
psql: FATAL: password authentication failed for user "gitlab"
Log from postgresql container
Initializing logdir...
Initializing rundir...
Setting resolv.conf ACLs...
Creating database user: gitlab
Creating database: gitlabhq_production...
‣ Loading pg_trgm extension...
‣ Granting access to gitlab user...
Starting PostgreSQL 9.5...
LOG: could not create IPv6 socket: Address family not supported by protocol
LOG: could not resolve "localhost": Name or service not known
LOG: disabling statistics collector for lack of working socket
WARNING: autovacuum not started because of misconfiguration
HINT: Enable the "track_counts" option.
LOG: database system was shut down at 2016-11-27 22:17:21 UTC
LOG: MultiXact member wraparound protections are now enabled
LOG: database system is ready to accept connections
My configuration
`docker run --name gitlab-postgresql -d
--env 'DB_NAME=gitlabhq_production'
--env 'DB_USER=gitlab' --env 'DB_PASS=password'
--env 'DB_EXTENSION=pg_trgm'
--volume /share/CACHEDEV1_DATA/VM/container-station-data/gitlab/postgresql:/var/lib/postgresql
sameersbn/postgresql:9.5-3
docker run --name gitlab-redis -d
--volume /share/CACHEDEV1_DATA/VM/container-station-data/gitlab/redis:/var/lib/redis
sameersbn/redis:latest
docker run --name gitlab -d
--link gitlab-postgresql:postgresql --link gitlab-redis:redisio
--publish 10022:22 --publish 10080:80
--env 'GITLAB_PORT=10080' --env 'GITLAB_SSH_PORT=10022'
--env 'GITLAB_SECRETS_DB_KEY_BASE=long-and-random-alpha-numeric-string'
--env 'GITLAB_SECRETS_SECRET_KEY_BASE=long-and-random-alpha-numeric-string'
--env 'GITLAB_SECRETS_OTP_KEY_BASE=long-and-random-alpha-numeric-string'
--volume /share/CACHEDEV1_DATA/VM/container-station-data/gitlab/gitlab:/home/git/data
sameersbn/gitlab:8.14.0`
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the PostgreSQL and GitLab docker run commands in the issue, especially DB_NAME, DB_USER, DB_PASS, the linked container name, and the mounted data directory. Compare those settings with the PostgreSQL container logs showing user creation, then reproduce the startup sequence and determine whether the authentication failure is caused by configuration or persisted database state. Done means the documented configuration starts GitLab successfully or the issue is closed with confirmed setup requirements.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, postgresql, shell
- Domain
- databases, devops
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100