Have Discussion for Nanoserver Requiring Parameters for PSGet commands

[anamnavi]

Currently there's a known issue in PowerShell-Docker for nanoserver subsystem where you have to specify -Scope CurrentUser and, for certain modules/cases, -SkipPublisherCheck for Install-Module. This is because the nanoserver API for the user subsystem that checks where to install has been disabled for nanoserver. The API is from the nanoserver side, but they half-removed/disabled the subsystem to switch user because nanoserver is intended for container use.

We could discuss adding a check for whether PSGet is being run on nanoserver and if so including these parameters onto the PSGet cmdlet, so that the user doesn't have to add it themselves.

[issue-label-bot]

Issue Label Bot is not confident enough to auto-label this issue. See dashboard for more details.

[SydneyhSmith]

We should consider if this could be done on the nanoserver side since the issue is distribution specific...you we adapt the nanoserver image to set the $PSDefaultParams ?

[TravisEz13]

That would work for the images we provide; we have no idea if people are building custom built images. This seems something important to fix as it seems to be our top windows distribution for PS7.