Docker Compose on Azure App Service randomly fails and doesn't work again

Muhammet 0 Reputation points
2024-03-03T22:26:55.44+00:00

I setup a docker compose with a reverse proxy on the nginx side. It seemed to have worked at first but after adding some app settings, it stopped working. I removed the app settings and it did not fix it.

I had this problem happen on 3 different apps. I know it is a preview feature but I don't see any other way other than using a VM which would add management overhead that I am trying to avoid.

Here is my docker compose:

version: "3.8"
services:
  webapp: 
    image: resource_name.azurecr.io/webapp:latest
    ports:
      - "80:80"
  wordpress:
    image: resource_name.azurecr.io/wordpress:latest
    restart: always
    ports:
      - 8080:80

At first, it loads the containers and the reverse proxy even works!

I have two theories.

  1. Updating the app settings bricks it and can't recover it.
  2. Adding an outbound v-net does it.

I couldn't pinpoint what does it.

Here is the error in the logs: Failed to load container logs: Resource containerlog of type text not found

Azure App Service
Azure App Service
Azure App Service is a service used to create and deploy scalable, mission-critical web apps.
7,769 questions
0 comments No comments
{count} votes

2 answers

Sort by: Most helpful
  1. Muhammet 0 Reputation points
    2024-03-03T23:18:07.3633333+00:00

    It was the Outbound V-Net. Removing it resolved the issue.


  2. Grmacjon-MSFT 17,876 Reputation points
    2024-04-09T19:06:19.74+00:00

    Hi @Muhammet I'm glad that you were able to resolve your issue and thank you for posting your solution so that others experiencing the same thing can easily reference this!

    Since the Microsoft Q&A community has a policy that "The question author cannot accept their own answer. They can only accept answers by others ", I'll repost your solution in case you'd like to "Accept" the answer.

    Issue:

    -You have a docker compose with a reverse proxy on the nginx side. It seemed to have worked at first but after adding some app settings, it stopped working.

    -You removed the app settings and it did not fix the issue. This problem occured for 3 different apps

    Solution:

    -Removing the outbound VNET resolved your issue

    Thanks,

    Grace

    0 comments No comments

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.