Unable to install IIS AspNetCoreModuleV2 in a dockerimage (and Azure Pipelines)
I have a problem for few days now with the “dotnet hosting bundle” and AspNetCoreV2 IIS module in a dockerimage.
I have a problem for few days now with the “dotnet hosting bundle” and AspNetCoreV2 IIS module in a dockerimage.
Visual studio runs docker with a lot of command line arguments when building/running. So hitting run in debug and release mode starts up the container with no issues.
I am trying to build my ASP.NET 4.7.2 WEB Services into a docker file, however when I run
I have installed IIS on docker, disabled any firewall and configure no-ip for access externalLy, and finally configured no-ip on my router with port fowarding…
I have configured iis and congirured local port 91 to 80 container port…
from local ‘http://pincopallino-no-ip:91’ compare correctly the default iis page, but externally network I get ‘err_connection_timed_out’….
I have been trying to get docker to pull from a private nuget feed which is hosted within Azure Devops, but I consistently get a 401 unauthorized error. I have looked a numerous other answers and resources, but all of which have not helped. My dockerfile script is the following
I am running into something that is extremely odd. I have the following stack:
We’re planning an architecture where asp.net websites must communicate with microservices.
The plan is to hos this in Azure, with the Website being an Azure ASP.NET Website and the microservices in Kubernetes/docker containers.
I was thinking kubenet was the way to go, so that a number of microservice instances could be spawned on demand without the need for the website to know about this, but it seems like VM-Kubernetes connectivity is not supported unless initiated by the Pod, or am I misunderstanding something?
https://docs.microsoft.com/en-us/azure/aks/concepts-network#azure-virtual-networks
I have a problem regarding Docker.
I want to containerize my ASP.Net Framework 4.6 application and I see the following base Images
TL;DR I added a cronjob to check if the docker daemon is running or not -> if not then restart the service. It works like a champ and I never met the issue again. * * * * * docker info > /dev/null || systemctl restart docker Please note that the cronjob should belong to … Read more