Problems with default H2 connection about docker-sonarqube

[Godin]

Can't reproduce using

$ docker version
Client:
 Version:      17.03.1-ce
 API version:  1.27
 Go version:   go1.8.3
 Git commit:   c6d412e
 Built:        Fri Jul 14 17:56:32 2017
 OS/Arch:      linux/amd64

Server:
 Version:      17.03.1-ce
 API version:  1.27 (minimum version 1.12)
 Go version:   go1.8.3
 Git commit:   c6d412e
 Built:        Fri Jul 14 17:56:32 2017
 OS/Arch:      linux/amd64
 Experimental: false

$ docker-compose version
docker-compose version 1.14.0, build c7bdf9e
docker-py version: 2.4.2
CPython version: 2.7.12
OpenSSL version: OpenSSL 1.0.2k  26 Jan 2017

$ docker images
REPOSITORY          TAG                 IMAGE ID            CREATED             SIZE
sonarqube           6.4                 7bbef44cb183        15 hours ago        890 MB

and docker-compose.yml:

version: "2"

services:
  sonarqube:
    image: sonarqube:6.4
    command: -Dsonar.web.context=/sonarqube
    ports:
      - "9000:9000"

server was up and working fine for more than 12 hours.

If you're using Azure, EC2 or similar container services, then maybe this exception is a consequence of the fact that infrastructure decides to stop container - please check with service provider.

There is no precedents of such exception outside of Docker and there is no magic in this Docker image - just a Java and bunch of SonarQube JAR files running as a Java application, so there is very high chances that your issue is related to your infrastructure.

Last but not least - as stated in SonarQube UI: "Embedded database should be used for evaluation purpose only", i.e. it is suitable only for short demos, but not for production use and especially for a long-running server instance. So don't be surprised about scalability and reliability issues - you have been warned.