Open MichaelSimons opened 3 years ago
That work around mentioned there only applies to ECS. All the error logs mentioned above are from me trying to run it on an EC2 instance using Docker. No orchestration platform is involved.
I can't get the images to run either unless I do not pass in any port binding or environment variables, but then the container is largely useless.
https://github.com/microsoft/dotnet-framework-docker/issues/1111
How does anyone get these containers to work? It looks like some people are getting them to work, but for me on my Windows 11 laptop, they just fail immediately. What am I missing?
@dasiths commented on Mon Nov 09 2020
The W3SVC doesn't start on the 4.8-windowsservercore-1909 image
I'm trying to run the image using docker run but keep running in to this error.
When defining the port it fails with a slightly different error
I also tried to create my own dockerfile from this image. In the build steps I tried calling
which failed with
Then I tried doing this
and when inside the container ran following commands to start w3svc with no success as well.
Steps to Reproduce
Other Information
Output of
docker version
Output of
docker info
@MichaelSimons commented on Mon Nov 09 2020
@HongGit - Can you help out with this issue?
@dasiths commented on Mon Nov 09 2020
it's possibly related to https://github.com/microsoft/IIS.ServiceMonitor/issues/34
@dasiths commented on Mon Nov 09 2020
I've just checked the same image on a Windows 10 pro machine with 2004 kernel version and it works. So it's tied to the Windows Data Centre version I tried before.
Here is the environment it fails in. It's running in an AWS EC2 instance.
@MichaelSimons commented on Tue Nov 10 2020
@dasiths - did you try the workaround mentioned here?
@shirhatti, I'm transferring this to IIS as this seems related to microsoft/IIS.ServiceMonitor#34.