Azure Docker Upgrade from 8.5.1 to 8.6.0 probelms


I am running SonarQube in Azure Container Instances and it is currently 8.5.1

I want to upgrade to 8.6.0 and it is causing me problems. To rollout new versions I simply delete the current Container Setup then with my template change the image version and recreate the Container Instance as the data and storage are external to the image. Usually this works fine.

I have tried the latest image on DockerHub sonarqube:8.5.1-developer however when the container tries to start it seems to get in to an endless loop of termination and restart. There is no log information I can see as it keeps restarting.

I haven’t even been able to get to the setup web page so this isn’t an issue.

Am I missing something or is there an issue with the image?

Thanks for the help

Hello @johnm and welcome to the community :wave:

do you have a volume for the logs to check if there is maybe something written in there? it is off that there is no log at all, as the first thing sonarqube does is to write something to the logs.
did you modify the limits according to our docs ? Also can you clarify what image is working for you? it is not clear to me if 8.5.1 is working / was working and is now crashing or if only the 8.6.0 image is not working for you

Also, are you using a PostgreSQL instance hosted on Azure?

Hi. Thanks for your suggestions. I assumed that the Docker Image was setup correctly.

We did however have a Log volume in Azure Storage (thanks for the pointer) that showed very little but it was all I needed.

This is the log

2021.01.13 21:40:25 INFO app[o.s.a.AppFileSystem] Cleaning or creating temp directory /opt/sonarqube/temp

2021.01.13 21:40:25 ERROR app[o.s.a.p.ManagedProcessHandler] Fail to launch process [es]

org.sonar.process.MessageException: Property ‘’ is no longer supported. Use ‘’ instead.

2021.01.13 21:40:25 INFO app[o.s.a.SchedulerImpl] Process[es] is stopped

2021.01.13 21:40:25 INFO app[o.s.a.SchedulerImpl] Waiting for Elasticsearch to be up and running

2021.01.13 21:40:25 INFO app[o.s.a.SchedulerImpl] SonarQube is stopped

So as it turned out our config was also stored in Azure storage and we had this setting

Which I had to change to this

Now all seems good.


This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.