container Failing to start about docker-sonarqube

[patrickmslatteryvt]

What I found when I used a MySQL DB was that the database name had to be sonar, so that might be hardcoded somewhere, I didn't dig into it too far.
For your other error use sh instead of bash as Alpine Linux does not include bash by default:

- docker exec -it sonarqube bash
+ docker exec -it sonarqube sh

[majinding]

now I running with raw "docker run -d --name sonarqube -p 9000:9000 -p 9092:9092 sonarqube" is ok
but when I command "docker exec -it sonarqube bash" was error "rpc error: code = 2 desc = oci runtime error: exec failed: container_linux.go:247: starting container process caused "exec: \"bash\": executable file not found in $PATH""

[Godin]

@patrickmslatteryvt First of all thank you for helping here! This is very much appreciated! ❤️

You're right about bash and Alpine image. 👍

However as shown below, I cannot reproduce any of problems with MySQL that were mentioned here including

when used a MySQL DB was that the database name had to be sonar, so that might be hardcoded somewhere

Maybe this was about default user and password for DB that are both sonar - see

docker-sonarqube/5.6.6/Dockerfile

Lines 7 to 8 in c6aa0bb

	SONARQUBE_JDBC_USERNAME=sonar \
	SONARQUBE_JDBC_PASSWORD=sonar \

---

After creation of MySQL with database named sq:

docker run --rm \
    --name db \
    -e MYSQL_DATABASE=sq \
    -e MYSQL_ROOT_PASSWORD=root-password \
    -e MYSQL_USER=user \
    -e MYSQL_PASSWORD=user-password \
    mysql

SonarQube succesfully connects to it:

docker run --rm \
    --link db:db \
    -e SONARQUBE_JDBC_URL="jdbc:mysql://db/sq?useUnicode=true&characterEncoding=utf8" \
    -e SONARQUBE_JDBC_USERNAME=user \
    -e SONARQUBE_JDBC_PASSWORD=user-password \
    sonarqube

as log shows:

...
2017.08.15 18:29:50 INFO  web[][o.sonar.db.Database] Create JDBC data source for jdbc:mysql://db/sq?useUnicode=true&characterEncoding=utf8
...
2017.08.15 18:29:52 INFO  web[][DbMigrations] Executing DB migrations...
2017.08.15 18:29:52 INFO  web[][DbMigrations] #1 'Create initial schema'...
2017.08.15 18:29:53 INFO  web[][DbMigrations] #1 'Create initial schema': success | time=1698ms
2017.08.15 18:29:53 INFO  web[][DbMigrations] #2 'Populate initial schema'...
...

---

@majinding

was not work

what was in log?

[patrickmslatteryvt]

@Godin You are correct, I tried to replicate the issue with my Ansible deployment scripts and was not able to make the Sonarqube install break when I changed the MySQL DB name.
I know I did have issues with this when I wrote the deployment scripts as I put this line in:

      mysql_database: sonar  # THE DB _MUST_ BE CALLED "sonar"

But it all works now! :-)

A few minor differences I had were that:

1. I used networks rather than links (which are deprecated) but that shouldn't break it
2. I used the MySQL image from Oracle (mysql/mysql-server)
3. I used Sonarqube v6.4 rather than v6.5, I tested with both just now and they both connect to MySQL DBs with names other than sonar

docker image pull mysql/mysql-server:5.7
docker image pull sonarqube:6.4
docker image pull sonarqube:6.5
docker network create sonarqube

docker run \
  -it \
  --rm \
  --name db \
  --env MYSQL_DATABASE=sq \
  --env MYSQL_ROOT_PASSWORD=root-password \
  --env MYSQL_USER=user \
  --env MYSQL_PASSWORD=user-password \
  --network=sonarqube \
  mysql/mysql-server:5.7

docker run \
  -it \
  --rm \
  --env SONARQUBE_JDBC_URL="jdbc:mysql://db/sq?useUnicode=true&characterEncoding=utf8&useSSL=false" \
  --env SONARQUBE_JDBC_USERNAME=user \
  --env SONARQUBE_JDBC_PASSWORD=user-password \
  --network=sonarqube \
  sonarqube:6.4

  2017.08.15 20:43:02 INFO  web[][o.s.s.p.d.m.AutoDbMigration] Automatically perform DB migration on fresh install
  2017.08.15 20:43:02 INFO  web[][DbMigrations] Executing DB migrations...
  2017.08.15 20:43:02 INFO  web[][DbMigrations] #1 'Create initial schema'...
  2017.08.15 20:43:03 INFO  web[][DbMigrations] #1 'Create initial schema': success | time=712ms
  2017.08.15 20:43:03 INFO  web[][DbMigrations] #2 'Populate initial schema'...
  2017.08.15 20:43:03 INFO  web[][DbMigrations] #2 'Populate initial schema': success | time=55ms
  <snip>
  2017.08.15 20:43:31 INFO  app[][o.s.a.SchedulerImpl] SonarQube is up

[majinding]

I'm sorry, I didn't know how to check the log before the container started

Now the reason for the problem has been found, because the mysql5.1 version is too low

Thanks @patrickmslatteryvt , @Godin