Getting connection reset while accessing azure container instance

Binod Kumar 20

Hi All,

I have created one docker image using dot net core and successfully pushed the image in container registry. After that I have published the same image in container app and container instance. I am not getting any issue in container app, but getting "the connection was reset" while accessing container instance.

PFB Docker file

FROM mcr.microsoft.com/dotnet/aspnet:8.0 AS base

USER $APP_UID

WORKDIR /app

EXPOSE 8080

EXPOSE 8081

FROM mcr.microsoft.com/dotnet/sdk:8.0 AS build

ARG BUILD_CONFIGURATION=Release

WORKDIR /src

COPY ["MyAPI/MyAPI.csproj", "MyAPI/"]

RUN dotnet restore "./MyAPI/MyAPI.csproj"

COPY . .

WORKDIR "/src/MyAPI"

RUN dotnet build "./MyAPI.csproj" -c $BUILD_CONFIGURATION -o /app/build

FROM build AS publish

ARG BUILD_CONFIGURATION=Release

RUN dotnet publish "./MyAPI.csproj" -c $BUILD_CONFIGURATION -o /app/publish /p:UseAppHost=false

FROM base AS final

WORKDIR /app

COPY --from=publish /app/publish .

ENTRYPOINT ["dotnet", "MyAPI.dll"]

My Container instance properties

OS type Linux
IP address 130.107.39.53 (Public)
SKU Standard
Azure Spot -
FQDN secondapp.f3creyh2cfg6gjhu.canadacentral.azurecontainer.io
DNS name label scope reuse Tenant
DNS name label secondapp
Ports 80, 8080, 8081
Restart policy On failure
Container count 1
Key management Microsoft-managed keys (MMK)

Please assist

Thanks in advance

Nagarjuna Reddy Yanna 250 Reputation points Microsoft External Staff

2025-03-07T17:05:32.6333333+00:00

Hi Binod Kumar,

Welcome to microsoft Q&A, Thankyou for posting your query here.

Your Dockerfile looks good for a .NET app. You've opened up ports 8080 and 8081 the right way, just like how .NET needs it.

Azure Container Instances (ACI) doesn't let you pick a specific "target port".

you can get your ports set up the way you need with the help of Azure's command-line tools.

Make sure you're signed into your Azure account with the command line tool by typing az login.

Then, you'll use the az container create command to make your container with the right ports.

az container create \

--resource-group <RESOURCEGROUP NAME> \

--name <ContainerName> \

--image <Image> \

--dns-name-label <DnsName> \

--ports 8080 \

--environment-variables ASPNETCORE_URLS="http://+:8080" \

--protocol TCP

If, after setting everything up, you're still having trouble connecting (like getting "Connection reset" errors),:

Use Azure's website or the command line tool to check your container's logs for any errors during startup.

Check to make sure no network security settings or firewalls are blocking the ports you're using.

If you've just set up a friendly DNS name for your container, give it a bit of time to start working everywhere.

Hope this helps you.

Please let us know if it was helpful and feel free to reach out if you have any further queries.

If you found the information useful, please click "Upvote" on the post to let us know.

Thank You
Binod Kumar 20 Reputation points

2025-03-09T08:04:09.28+00:00

I am using below command to create container instance but getting issue

az container create --resource-group ContainerResources --name fourthcontainer --image myregistrybin/myapi:latest --dns-name-label myapibin --ports 8080 --protocol TCP --os-type Linux --cpu 2 --memory 3.5

Error

(InaccessibleImage) The image 'myregistrybin/myapi:latest' in container group 'fourthcontainer' is not accessible. Please check the image and registry credential.

Code: InaccessibleImage

Message: The image 'myregistrybin/myapi:latest' in container group 'fourthcontainer' is not accessible. Please check the image and registry credential.

Share via

Getting connection reset while accessing azure container instance

Your answer