Known Issues

Known Issues

PowerShell

Windows 20H2 Images and newer

We have an infrastructure issue building 20H2 images and newer. For more details see: https://github.com/PowerShell/PowerShell-Docker/issues/552

Work around

Manually build the image you need.

• Preview
  • Windows Server Core - https://github.com/PowerShell/PowerShell-Docker/tree/master/release/preview/windowsservercore20H2/docker
  • NanoServer - https://github.com/PowerShell/PowerShell-Docker/tree/master/release/preview/nanoserver20H2
• Stable
  • Windows Server Core - https://github.com/PowerShell/PowerShell-Docker/tree/master/release/stable/windowsservercore20H2/docker
  • NanoServer - https://github.com/PowerShell/PowerShell-Docker/tree/master/release/stable/nanoserver20H2/docker
• LTS
  • Windows Server Core - https://github.com/PowerShell/PowerShell-Docker/tree/master/release/lts/windowsservercore20H2/docker
  • NanoServer - https://github.com/PowerShell/PowerShell-Docker/tree/master/release/lts/nanoserver20H2/docker

Start-Process

There is no -verb on the Start-Process cmdlet.

ARM and Qemu not supported

Running an ARM image in QEMU is not supported.
This in a .NET Core requirement. https://github.com/dotnet/dotnet-docker/blob/b311acc7317d56f0ad16cc17b45d552503871bc4/samples/dotnetapp/README.md#build-an-image-for-arm32-and-arm64

You can build ARM32 and ARM64 images on x64 machines, but you will not be able to run them. Docker relies on QEMU for this scenario, which isn't supported by .NET Core. You must test and run .NET Core images on actual hardware for the given processor type. A common pattern for this situation is building on x64, pushing images to a registry, and then pulling the image from an ARM device.

WSMan does not work on most Linux images.

Please see: https://github.com/MicrosoftDocs/PowerShell-Docs/issues/6491

Images know not to work:

• lts-debian-10
• preview (Linux version)

Community Workaround

Please see: https://github.com/jborean93/omi

NanoServer Release Notes

General

NanoServer is affected by changes to the user subsystem. See [known issues with nano-server][user-subsystem-issue].

PowerShell Get

Only works with CurrentUser Scope

Due to known issues with the nano-server, you must specify -Scope CurrentUser when using Install-Module. Example:

Install-Module <ModuleName> -Scope CurrentUser

May require -SkipPublisherCheck

PowerShell get uses an API to verify signing that is unavailable on nanoserver. You may have to run the command with the following paramaters to get certain modules to install:

Install-Module -Name Pester -Force -SkipPublisherCheck