@Akthem Rehab , I went through the lab as well, using wordpress:latest
as the container instance and didn't have any issues. Assuming the az container create
completed successfully, check to make sure container instance actually deployed successfully. Did you use the correct password for the registry i.e. az acr credentials show --name myregistry
? Is it in a running state? Check for any errors in the log tab of the Containers blade that may have prevented the container from starting up and receiving traffic.
---
EDIT 2022 November 14 I used rocker/rstudio
image which exposes port 8787 just as your docker image does. I configured the container instance with the following CLI command az container create --name qna1085919 --image .azurecr.io/qna1085919:latest --dns-name-label qna1085919 --registry-username <registry name> --registry-password <password> --environment-variables PASSWORD=demopass@1224 --ports 8787
. I was then able to navigate to the instance via the 8787 port http://qna1085919.eastus.azurecontainer.io:8787/. Your setting port 443 which your app is not accepting traffic on. You should be able to adjust your docker image through the EXPOSE
command i.e 8787:80
so that HTTP traffic gets forwarded to that open port. Another option is configure your docker image so that your rocker/r-base
is configured to accept traffic on port 80/443.