# SQ 8.5 Docker image using Azure Postgressql

**URL:** <https://community.sonarsource.com/t/sq-8-5-docker-image-using-azure-postgressql/32613>\
**Category:** SonarQube Server / Community Build\
**Tags:** docker\
**Created:** [October 8, 2020, 11:34am UTC](https://community.sonarsource.com/t/sq-8-5-docker-image-using-azure-postgressql/32613 "2020-10-08T11:34:16Z")\
**Posts on this page:** 1\
**Showing post:** 10

<div class="post-metadata">

**Author:** ![Tobias\_Trabelsi](https://dub1.discourse-cdn.com/sonarsource/user_avatar/community.sonarsource.com/tobias_trabelsi/32/31755_2.png) [@Tobias\_Trabelsi](https://community.sonarsource.com/u/Tobias_Trabelsi)\
**Post date:** [October 12, 2020, 1:51pm UTC](https://community.sonarsource.com/t/sq-8-5-docker-image-using-azure-postgressql/32613/10 "2020-10-12T13:51:13Z")

</div>

Hi @Jos_Wilbrink ,

we did some investigation and noticed that we upgraded the postgresql jdbc driver by 2 patch versions ( `42.2.14` to `42.2.16` ). and with that we dug deeper if there are any issues with this version connected to azure, and indeed there is one [documented in the azure docs](https://docs.microsoft.com/en-us/azure/postgresql/concepts-limits) that hits what you observed perfectly!  
please try to disable GSS explicitly in the connect string, so like this:

`jdbc:postgresql://xxxxx.postgres.database.azure.com:5432/xxxx?gssEncMode=disable`

---

_[View the full topic](https://community.sonarsource.com/t/sq-8-5-docker-image-using-azure-postgressql/32613)._