12/3/2023 0 Comments Azure mysql in appThe attempts to redeploy the app using a specific MySQL container image that was up to date when I created the original Docker Compose configuration didn’t succeed. Unfortunately, I didn’t find any mentions of service updates in the official docs or on community resources.Īnother possible cause of the error could be some updates to the MySQL container image – I was using the image with the ‘mysql:5.7’ tag and didn’t stick to a specific build in that minor version. Nothing was changed in the deployment configuration, and I started looking for possible root causes of that issue.Īs the multi-container support on App Service is still in preview, changes to that service might have caused the containers to crash. However, starting from May 2021, I received a few notifications indicating that the original deployment configuration stopped working, and the following error occurred in App Service container logs:ĮR_HOST_NOT_PRIVILEGED: Host ‘172.X.X.X’ is not allowed to connect to this MySQL server I was able to reduce the application hosting costs by hosting MySQL as a container on the same App Service plan as the Ghost container itself. In Dec 2020, when I come up with the idea of hosting Ghost on Azure as a multi-container app using Docker Compose support in Azure App Service, that configuration worked fine. Why fall back to managed MySQL server from the multi-container app If you are more interested in the technical details, feel free to skip my reasoning for using Azure Database for MySQL as a backed for Ghost in the first section and scroll straight to the second one. Moreover, in this post, I will shed some light on doing it securely from any Node.js application. Continuing the topic of hosting Ghost on Azure, I decided to document some nuances of connecting to Azure Database for MySQL from a Ghost Docker container hosted on Azure Web Apps for Containers.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |