Hi Binod Kumar,

Welcome to the Microsoft Q&A Platform! Thank you for asking your question here.

Based on our understanding of your issue, we recommend that you refer to the following methods for troubleshooting:

The "connection reset" error encountered while trying to access your Azure Container Instance may arise from multiple factors, including improper port configuration, network security settings, or application-related issues. It is crucial to examine the container logs, confirm that the correct ports are exposed, and ensure that your application is configured to listen on the designated IP address.

• Check the logs for any errors or exceptions by using Azure CLI:

az container logs --resource-group <YourResourceGroup> --name <YourContainerName>

Ensure that the ports are correctly exposed to your application. When creating the container instance, specify the ports:

az container create --resource-group <YourResourceGroup> --name <YourContainerName> --image <YourImage> --ports <PortNumber>

• If the container instance is integrated within a Virtual Network (VNet), ensure that there are no network security group (NSG) rules or firewall configurations that may delay access to the container.
• Ensure that the Network Security Group (NSG) linked to your container instance permits inbound traffic on the necessary ports. Modify the rules as needed within the Azure Portal.
• Test the IP address with curl or telnet to verify if the container instance is responding or not.

curl http://<container-ip>:<port>

• Restart the container instance to resolve any issues:

az container restart --resource-group <YourResourceGroup> --name <YourContainerName>

If you found it helpful, could you kindly click the “Accept Answer and upvote” on the post.

If you have any further queries, please let us know we are glad to help you.

Hi Binod Kumar,

Just checking in to see if you have got a chance to see my response to your question in resolving the issue.

If it was helpful, please click "Upvote" on this post to let us know.

Thank You.

Dear Suresh

I have not used any vnet or NSG configuration. Simply I have just pushed one image from visual studio to container registry. Docker file I have already shared above. After that I am creating container instance with default settings. I have selected network type as public only and added the ports.

please suggest

Dear Suresh

I have not used any vnet or NSG configuration. Simply I have just pushed one image from visual studio to container registry. Docker file I have already shared above. After that I am creating container instance with default settings. I have selected network type as public only and added the ports.

Hi Binod Kumar,

Based on the issue description shared, seems like you are having trouble accessing your accessing azure container instance Registry.

To troubleshoot this issue, you can try the following steps:

# Use the SDK image to build the app
FROM mcr.microsoft.com/dotnet/sdk:6.0 AS build
WORKDIR /src
COPY ["MyAPI/MyAPI.csproj", "MyAPI/"]
RUN dotnet restore "MyAPI/MyAPI.csproj"
COPY . .
WORKDIR "/src/MyAPI"
RUN dotnet build "MyAPI.csproj" -c Release -o /app/build
# Publish the app
FROM build AS publish
RUN dotnet publish "MyAPI.csproj" -c Release -o /app/publish
# Final stage/image
FROM mcr.microsoft.com/dotnet/aspnet:6.0 AS final
WORKDIR /app
COPY --from=publish /app/publish.
ENTRYPOINT ["dotnet", "MyAPI.dll"]

Check if your Azure subscription has sufficient resources available in the region where your container instance is deployed. Resource constraints can lead to connection issues.

Verify that the image name and tag are correct.

az acr repository show-tags --name <registry-name> --repository <repository-name>

Verify that the registry credentials are correct. You can check this by running the following command in the Azure CLI:

az acr login --name <registry-name>

Ensure that the image you are trying to pull exists in your Azure Container Registry. You can use the following command to list the images in your registry:

az acr repository list --name <registry-name> --output table

Check if you have the correct permissions to access the image. You can use the following command to check the permissions:

az acr repository show --name <registry-name> --repository <repository-name> --output table

• If you are using a private subnet, make sure that the subnet has access to the internet. You can do this by adding a NAT gateway to the subnet.
• Make sure that the IP address of the subnet is added to the "Networking" allowed IP's in the Azure Container Registry.

Please look into below documents for more Information:

https://learn.microsoft.com/en-us/troubleshoot/azure/azure-container-instances/configuration-setup/inaccessible-image

https://learn.microsoft.com/en-us/azure/container-registry/allow-access-trusted-services#about-trusted-services

If you found it helpful, could you kindly click the “upvote” on the post.