Kirsten Kluge

Hello @StefanScherer I solved it by building my own Image based on your docker file with this base Image: ``` mcr.microsoft.com/powershell:nanoserver-2004 ``` And I had to replace `containeruser` with `containeradmin`...

Hi, for every one using PowerShell: ``` .\node_modules\.bin\typings.cmd ls | foreach{ $package =$_.split(" ",[StringSplitOptions]'RemoveEmptyEntries')[1]; Write-Output $package .\node_modules\.bin\typings.cmd i -SG $package } ``` cu, KirK

I have the same issue on windows server core. Sometimes it does not start at all. Tried with the latest version.

thanks to @StefanScherer and his work on https://github.com/StefanScherer/docker-cli-builder/ there is a way to get the file, but in my opinion there should be an official way to get this.

Hey @itzg you pointed us in the right direction! Indeed, there was a problem with the Time settings in our docker host. So, the time was wrong in the container....

good point. The latest Tag is over 3 years old. This needs to be added to the pipeline, I think. I will have a look int this but it might...