You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The ContainerUser powershell module path should be in the PSModulePath env variable so that the installed module is available in both interactive container runs or for building images with modules packaged.
Actual behavior
The module installs but is not usable unless the PSModulePath env var is manipulated every session or as part of the image entrypoint, e.g. a script that first sets up the PSModulePath by hand then continues on to do whatever the image's intended work is. (We are currently doing this.)
Issue-Label Bot is automatically applying the label Issue-Bug to this issue, with a confidence of 0.90. Please mark this comment with 👍 or 👎 to give our bot feedback!
Steps to reproduce
** Note attempting to run Install-Module with -Scope AllUsers fails due to permissions
Expected behavior
The ContainerUser powershell module path should be in the PSModulePath env variable so that the installed module is available in both interactive container runs or for building images with modules packaged.
Actual behavior
The module installs but is not usable unless the PSModulePath env var is manipulated every session or as part of the image entrypoint, e.g. a script that first sets up the PSModulePath by hand then continues on to do whatever the image's intended work is. (We are currently doing this.)
Environment data
The text was updated successfully, but these errors were encountered: