mthalman
commented
4 years ago I just tried this scenario and it worked for me. Here's the steps I took:
- Create a new project in Visual Studio using the ASP.NET Core Web Application template.
- Modify the generated Dockerfile to use
3.1-alpinetags instead of3.1-buster-slimor3.1-buster. - Modify the base stage of the Dockerfile to include:
ENV DOTNET_SYSTEM_NET_HTTP_SOCKETSHTTPHANDLER_HTTP2SUPPORT=true ENV DOTNET_SYSTEM_GLOBALIZATION_INVARIANT=false ENV ASPNETCORE_ENVIRONMENT=Production RUN apk add --no-cache icu-libs - Publish the image to Docker Hub.
- Create a new Azure App Service that references the image tag that was published to in Docker Hub.
- Navigate to the app in the browser.
App loads fine. The log output shows this at the end:
2020-07-15T13:38:32.922Z INFO - Starting container for site
2020-07-15T13:38:32.923Z INFO - docker run -d -p 3283:80 --name mthalman-webapp_0_aceeed9b -e WEBSITES_ENABLE_APP_SERVICE_STORAGE=false -e WEBSITE_SITE_NAME=mthalman-webapp -e WEBSITE_AUTH_ENABLED=False -e PORT=80 -e WEBSITE_ROLE_INSTANCE_ID=0 -e WEBSITE_HOSTNAME=mthalman-webapp.azurewebsites.net -e WEBSITE_INSTANCE_ID=b58ed186e2b61004b35a91eecc2993dae826e74b0fc1745b541dd38dfc4c05ef mthalman/webapplication9:webapp
2020-07-15T13:38:32.924Z INFO - Logging is not enabled for this container.
Please use https://aka.ms/linux-diagnostics to enable logging to see container logs here.
2020-07-15T13:38:34.664Z INFO - Initiating warmup request to container mthalman-webapp_0_aceeed9b for site mthalman-webapp
2020-07-15T13:38:37.074Z INFO - Container mthalman-webapp_0_aceeed9b for site mthalman-webapp initialized successfully and is ready to serve requests.If you could provide steps like this that repro the issue, that'd be very helpful.
JMan7777
MichaelSimons
Hello,
I have a strange problem. I'm running a web app for Linux (.NET Core 3.1.6) under Azure and using the docker images from MS. I was using the Alpine 3.11 images (3.1-alpine3.11) and had no issues with my application. Also with the Ubuntu docker images (3.1-bionic) my application works fine. However when I just switch from the 3.1-alpine3.11 to the 3.1-alpine (aka Alpine 3.12) images my application builds fine but during startup in Azure I get the error message below.
2020-07-15T08:13:17.998Z ERROR - Container xxx_0_6e260ec1 for site xxx has exited, failing site start2020-07-15T08:13:18.008Z ERROR - Container xxx_0_6e260ec1 didn't respond to HTTP pings on port: 80, failing site start. See container logs for debugging.2020-07-15T08:13:18.011Z INFO - Stopping site xxx because it failed during startup.I see no application errors in the docker output files.
My dockerfile in VisualStudio which I use to build the app looks as follows (for Alpine 3.11):
FROM mcr.microsoft.com/dotnet/core/aspnet:3.1-alpine3.11 AS baseWORKDIR /appEXPOSE 80EXPOSE 443ENV DOTNET_SYSTEM_NET_HTTP_SOCKETSHTTPHANDLER_HTTP2SUPPORT=trueENV DOTNET_SYSTEM_GLOBALIZATION_INVARIANT=falseENV ASPNETCORE_ENVIRONMENT=ProductionRUN apk add --no-cache icu-libsFROM mcr.microsoft.com/dotnet/core/sdk:3.1-alpine3.11 AS buildWORKDIR /srcCOPY ["MYAPP/MYAPP.csproj", "MYAPP/"]RUN dotnet restore "MYAPP/MYAPP.csproj"COPY . .WORKDIR "/src/MYAPP"RUN dotnet build "MYAPP.csproj" -c Release -o /appFROM build AS publishRUN dotnet publish "MYAPP.csproj" -c Release -o /appFROM base AS finalWORKDIR /appCOPY --from=publish /app .ENTRYPOINT ["dotnet", "MYAPP.dll"]If I just change
3.1-alpine3.11to3.1-alpinefor the aspnet and the sdk images I get the error as mentioned above.Since Alpine 3.11 will be obsolete soon I assume and since I do not want to use a bigger Linux image (like the Ubuntu images) can you please kindly have a look on the issue.
Thx a lot.
Cheers, Markus