New-PSUEnvironment -PSModulePath Issue with Linux

PowerShell Universal
1 
Product: PowerShell Universal
Version: 1.5.13 (Ubuntu Docker)

I’m seeing an issue when trying to add another module path to PSModule by, either by the GUI or with the New-PSUEnvironment cmdlet

New-PSUEnvironment -Name “Posh7” -Path “/usr/bin/pwsh” -PSModulePath @(‘/home/.PowerShellUniversal/Repository/Modules’)

image
image1417×232 23.2 KB

Looks like PSU is appending $env:PSModulePath with a ; instead of a : which isn’t valid for Linux.

This really wouldn’t be a problem for me, but for some reason PSU isn’t respecting the actual PSModulePath environmental variable from the Docker container that I set in the docker file.

ENV PSModulePath=/root/.local/share/powershell/Modules:/usr/local/share/powershell/Modules:/opt/microsoft/powershell/7/Modules:/home/.PowerShellUniversal/Repository/Modules

Kinda two separate issues, but when one way didn’t work tried to find another way…

2

Somewhat related, I’ve also noticed that the variables int he example are relative paths and it makes things a bit screwy.

Changing them to absolute paths in the docker variables appears to fix things.
I still have to import modules using the full path though, haven’t figured that one out yet.
Issue open here. Docker container switches between relative and absolute paths · Issue #101 · ironmansoftware/powershell-universal · GitHub