Closed artisticcheese closed 5 years ago
@NikolaMilosavljevic - @dleeapho asked if you could take a look at this? My initial look makes me suspicious this is an issue with both the 1809 and 1803 images. I wonder if Windows isn't re-running ngen after applying the .net LCU.
Running 'ngen update' definitely fixes the issue. Following up with Windows owners to understand their imaging process.
Assigning to Matt to validate. I see Windows has resolved the their infrastructure issue which is the supposed source of the underlying issue.
@MichaelSimons - This doesn't seem to be resolved in the base image.
docker run --rm mcr.microsoft.com/dotnet/framework/runtime:4.7.2-windowsservercore-1803 powershell -Command (Measure-Command { powershell -command exit }).TotalSeconds
Result: 2.187819
@NikolaMilosavljevic - What was the result of your follow-up with the Windows team?
Please see this announcement https://github.com/dotnet/announcements/issues/33 2019 Dockerfile missing all NGEN optimization stuff looks like.