Project & issues history go missing at Docker's restart

[tsukino...@hotmail.com]

Hi,

Our IT and us (QA) worked so that our SonarQbe runs using Docker. We use SonarQbe 6.4.

However each time we restart the docker, we lose the history: the project list (menu "Projects") & issues (menu "Issues") are empty (even though the counter says "1 projects" on the left top). Is it "work as design" not to see the last iterations at the docker restart?

System Logs (Administration section > System > System Info > Logs > Compute Engine):

2017.08.10 09:26:19 INFO  ce[][o.s.p.ProcessEntryPoint] Starting ce
2017.08.10 09:26:19 INFO  ce[][o.s.ce.app.CeServer] Compute Engine starting up...
2017.08.10 09:26:20 INFO  ce[][o.e.plugins] [Goliath] modules [], plugins [], sites []
2017.08.10 09:26:20 INFO  ce[][o.s.s.e.EsClientProvider] Connected to local Elasticsearch: [127.0.0.1:9001]
2017.08.10 09:26:20 INFO  ce[][o.sonar.db.Database] Create JDBC data source for jdbc:mysql://10.32.50.137:3307/sonar?useUnicode=true&characterEncoding=utf8&rewriteBatchedStatements=true
2017.08.10 09:26:21 INFO  ce[][o.s.s.p.ServerFileSystemImpl] SonarQube home: /opt/sonarqube
2017.08.10 09:26:22 INFO  ce[][o.s.c.c.CePluginRepository] Load plugins
2017.08.10 09:26:22 INFO  ce[][o.s.c.q.PurgeCeActivities] Delete the Compute Engine tasks created before Sat Feb 11 09:26:22 GMT 2017
2017.08.10 09:26:22 INFO  ce[][o.s.ce.app.CeServer] Compute Engine is operational

Our database is not on the docker, and systems reconnect correctly after the docker restart. It's not a big problem (as I can rerun analysis) but I just wondered how "normal" it was, and/or if I could "fix" my setup to prevent this in any way.

Thanks,

San.

[G. Ann Campbell]

Hi San,

The next time you restart your container, can you try deleting $SONARQUBE_HOME/data/es before you start up SonarQube?

Ann