microsoft / iis-docker

Dockerfile for IIS
https://hub.docker.com/r/microsoft/iis/
MIT License
288 stars 128 forks source link

Problems with Install-WindowsFeature #172

Closed yuriipaneiko closed 4 years ago

yuriipaneiko commented 4 years ago

I am tring to deploy .net framework application in IIS container. But i need to install Web-Asp-Net45, and all worked fine in my laptop, but when i tried to make the same on build server ( Windows Server 2016) it failed, and i can not find the solution. image When i tried to make the same using DISM i encouneterd with the same error code 0x800f0922 Also i have problems with choco installing on it, but it is not so important Does anyone have ideas about how to solve it?

Ankit3794 commented 4 years ago

@Fufe1ok Which base image you are using for windows server 2016?

yuriipaneiko commented 4 years ago

@Fufe1ok Which base image you are using for windows server 2016?

@Ankit3794 I try to use several images, currently i use image, which was pulled, just using docker pull microsoft/iis but also i had same problem on mcr.microsoft.com/windows/servercore/iis:windowsservercore-ltsc2016 image I check just now, microsoft/iis and mcr.microsoft.com/windows/servercore/iis:windowsservercore-ltsc2016 have the same id, so i think that they are the same images

Ankit3794 commented 4 years ago

@Fufe1ok Can you try with this image docker pull mcr.microsoft.com/dotnet/framework/aspnet this image?

That image includes

yuriipaneiko commented 4 years ago

@Fufe1ok Can you try with this image docker pull mcr.microsoft.com/dotnet/framework/aspnet this image?

That image includes

* Windows Server Core as the base OS

* IIS 10 as Web Server

* .NET Framework (multiple versions available)

* .NET Extensibility for IIS

@Ankit3794 thank you a lot, it work))

jhkimnew commented 4 years ago

Hi @Ankit3794, this is a known issue. Probably this will be fixed in the next build.

https://support.microsoft.com/en-us/help/4542617/you-might-encounter-issues-when-using-windows-server-containers-with-t

FYI, the workaround of this known issue is to match the host’s version with the container’s version.