Sonarqube docker image 8.2 failing in azure web app backed by azure sql

I was trying to install sonarqube community edition in azure web app container backed up by azure sql.

Hosted : Azure Web Apps Container using sonarqube docker image
Database : Azure SQL [ I have already configured JDBC_URL, JDBC_USERNAME, JDBC_PASSWORD

Issue:
When I try to install the docker 8.2 community edition I am getting “didn’t respond to HTTP pings on port: 9000, failing site start”. However, when I use docker 7.1 image, everything works like a charm with the same database and environment configuration.

Also, 8.2 community docker image works with “Embedded database”. For this, to work I need to remove all settings mentioned below from web app’s app settings. I need Azure SQL, not Embedded database.

SONARQUBE_JDBC_URL:
jdbc:sqlserver://xxx-sql.xxx.mock.net:1433;databaseName=sonar;trustServerCertificate=false;hostNameInCertificate=*.database.windows.net;loginTimeout=30;
SONARQUBE_JDBC_USERNAME: username
SONARQUBE_JDBC_PASSWORD: password

Logs:
2020-04-18 07:21:06.632 INFO - Pull Image successful, Time taken: 2 Minutes and 56 Seconds
2020-04-18 07:21:06.713 INFO - Starting container for site
2020-04-18 07:21:06.714 INFO - docker run -d -p 1345:9000 --name sonarapp_0_338a176e -e WEBSITE_SITE_NAME=sonarapp -e WEBSITE_AUTH_ENABLED=False -e PORT=9000 -e WEBSITE_ROLE_INSTANCE_ID=0 -e WEBSITE_HOSTNAME=xxx.mywebsites.net -e WEBSITE_INSTANCE_ID=c5ca023cf00c2c55d26fd9fde28b31ebeba5d4ab2694580a387d9fd4508b6a79 sonarqube:8.2-community

2020-04-18 07:21:08.556 INFO - Initiating warmup request to container sonarapp_0_338a176e for site sonarapp
2020-04-18 07:21:25.891 INFO - Waiting for response to warmup request for container sonarapp_0_338a176e. Elapsed time = 17.3347129 sec
2020-04-18 07:21:41.515 INFO - Waiting for response to warmup request for container sonarapp_0_338a176e. Elapsed time = 32.9587954 sec
2020-04-18 07:21:57.199 INFO - Waiting for response to warmup request for container sonarapp_0_338a176e. Elapsed time = 48.6427778 sec
2020-04-18 07:22:01.392 ERROR - Container sonarapp_0_338a176e for site sonarapp has exited, failing site start
2020-04-18 07:22:01.414 ERROR - Container sonarapp_0_338a176e didn’t respond to HTTP pings on port: 9000, failing site start. See container logs for debugging.
2020-04-18 07:22:01.500 INFO - Stoping site sonarapp because it failed during startup.

2020-04-18T07:22:00.087917276Z ERROR: [1] bootstrap checks failed
2020-04-18T07:22:00.088256776Z [1]: max virtual memory areas vm.max_map_count [65530] is too low, increase to at least [262144]
2020-04-18T07:22:00.100269377Z 2020.04.18 07:22:00 INFO es[o.e.n.Node] stopping …
2020-04-18T07:22:00.169328487Z 2020.04.18 07:22:00 INFO es[o.e.n.Node] stopped
2020-04-18T07:22:00.170034887Z 2020.04.18 07:22:00 INFO es[o.e.n.Node] closing …
2020-04-18T07:22:00.286806602Z 2020.04.18 07:22:00 INFO es[o.e.n.Node] closed
2020-04-18T07:22:00.475175028Z 2020.04.18 07:22:00 WARN app[o.s.a.p.AbstractManagedProcess] Process exited with exit value [es]: 78
2020-04-18T07:22:00.478287728Z 2020.04.18 07:22:00 INFO app[o.s.a.SchedulerImpl] Process[es] is stopped
2020-04-18T07:22:00.478300228Z 2020.04.18 07:22:00 INFO app[o.s.a.SchedulerImpl] SonarQube is stopped

Hello,

I think you need to work on below:

2020-04-18T07:22:00.087917276Z ERROR: [1] bootstrap checks failed
2020-04-18T07:22:00.088256776Z [1]: max virtual memory areas vm.max_map_count [65530] is too low, increase to at least [262144]

Please have a look here Sonarqube docker-compose Failed to connect to hostname/192.168.32.3:9000 for reference.

Hope that helps.
Kris