FATAL: password authentication failed for user "sonar"

[larruda]

After upgrading to 6.1, 6.2, 6.3 or 6.3.1 images (alpine or not), my instance keeps failing with this message. The password is correct and available through the SONARQUBE_JDBC_PASSWORD environment variable set as a secret in Kubernetes. If I go back to 6.0, it just works.

Did something change regarding connecting to the database?

[jarrod-marshall]

Having the same problem as well.

[Godin]

Cannot reproduce using PostgreSQL:

docker run -it --rm --name some-postgres \
  -e POSTGRES_USER=myuser \
  -e POSTGRES_PASSWORD=mysecretpassword \
  -e POSTGRES_DB=sonar \
  postgres

docker run -it --rm --name sonarqube \
  -p 9000:9000 \
  --link some-postgres:postgres \
  -e SONARQUBE_JDBC_USERNAME=myuser \
  -e SONARQUBE_JDBC_PASSWORD=mysecretpassword \
  -e SONARQUBE_JDBC_URL=jdbc:postgresql://postgres:5432/sonar \
  sonarqube:6.3.1-alpine

second container with SonarQube 6.3.1 successfully connects to the first one.

Answering on the question

Did something change regarding connecting to the database?

This repository contains files to build Docker image for SonarQube and nothing more, i.e. not the SonarQube itself. The only changes in this repository between image for 6.0 and image for 6.3.1 are updates of SonarQube version - 5dc2733...476d459 About the changes in SonarQube itself please refer to its repository changelog/release notes/upgrade notes. But AFAIK there were no changes in regards to database connection. For the questions about SonarQube you'd better reach out to wider audience of community - there are various communication channels, such as Google Group: https://www.sonarqube.org/community/

In absence of clear steps to reproduce the issue and hence evidences that there is a problem specifically in files for image and not in a particular setup/environment, I'm closing this ticket.

Thank you for your understanding.

[larruda]

@jarrod268 please let me know if somehow you find to solve the issue.
Thanks @Godin for the explanation.

[jarrod-marshall]

This works fine on a VM with the latest version of docker-compose, however the Azure extension for docker is behind a little on the docker-compose version and they may be the culprit for me.