I won’t be able to provide the docker file so I’ll try to provide as much context as I can to the issue. I keep running into issues with Azure and Windows based Docker containers randomly. The app will run fine for weeks with no issues and then suddenly bug out (using the same exact image) and go into an endless cycle of "Waiting for container to be start." followed by "Container failed to reach the container’s http endpoint".
I have been able to resolve the issue in the past by re-creating the service (again using the same exact image) but it seems this time its not working.
- The same exact docker image runs locally no problem
- As I mentioned, re-creating the service before did the trick (using the same exact image)
Below are the exact steps I have in place:
- Build a windows based image using a Docker Compose File. I specify in the docker compose file to map ports 2000:2000.
- Push the Docker Image to a private repository on docker hub
- Create a web app service in Azure using the image
Any thoughts on why this randomly happens? My only next idea is to re-create the docker image as a Linux based image.
Source: Docker Questions