Install-Module is broken in preview 3 on Ubuntu 18.04 on WSL

[alastairs]

From @alastairs on July 11, 2018 12:9

Steps to reproduce

1. Install Windows Subsystem for Linux on Windows 10
2. Install Ubuntu 18.04
3. Install PowerShell Core 6.1 preview 3

Install-Module -Name Azure -Force
Get-Module -ListAvailable

Expected behavior

The output should contain the installed module, e.g.

> Get-Module -ListAvailable

ModuleType Version    Name                                ExportedCommands
---------- -------    ----                                ----------------
Script     5.1.2      Azure                               {Get-AzureAutomationCertificate, Get-AzureAutomationConnection, New-Azur...
Manifest   1.1.0.0    Microsoft.PowerShell.Archive        {Compress-Archive, Expand-Archive}
Manifest   3.0.0.0    Microsoft.PowerShell.Host           {Start-Transcript, Stop-Transcript}
Manifest   3.1.0.0    Microsoft.PowerShell.Management     {Add-Content, Clear-Content, Clear-ItemProperty, Join-P...
Manifest   3.0.0.0    Microsoft.PowerShell.Security       {Get-Credential, Get-ExecutionPolicy, Set-ExecutionPoli...
Manifest   3.1.0.0    Microsoft.PowerShell.Utility        {Format-List, Format-Custom, Format-Table, Format-Wide...}
Script     0.0        PSDesiredStateConfiguration         {ValidateNoNameNodeResources, Set-PSTopConfigurationNam...
Script     2.0.0      PSReadLine                          {Get-PSReadLineKeyHandler, Set-PSReadLineKeyHandler, Re...
Script     1.1.7.0    PackageManagement                   {Find-Package, Get-Package, Get-PackageProvider, Get-Pa...
Script     1.6.0      PowerShellGet                       {Install-Module, Find-Module, Save-Module, Update-Modul...

Actual behavior

The output does not contain the installed module

> Get-Module -ListAvailable

ModuleType Version    Name                                ExportedCommands
---------- -------    ----                                ----------------
Manifest   1.1.0.0    Microsoft.PowerShell.Archive        {Compress-Archive, Expand-Archive}
Manifest   3.0.0.0    Microsoft.PowerShell.Host           {Start-Transcript, Stop-Transcript}
Manifest   3.1.0.0    Microsoft.PowerShell.Management     {Add-Content, Clear-Content, Clear-ItemProperty, Join-P...
Manifest   3.0.0.0    Microsoft.PowerShell.Security       {Get-Credential, Get-ExecutionPolicy, Set-ExecutionPoli...
Manifest   3.1.0.0    Microsoft.PowerShell.Utility        {Format-List, Format-Custom, Format-Table, Format-Wide...}
Script     0.0        PSDesiredStateConfiguration         {ValidateNoNameNodeResources, Set-PSTopConfigurationNam...
Script     2.0.0      PSReadLine                          {Get-PSReadLineKeyHandler, Set-PSReadLineKeyHandler, Re...
Script     1.1.7.0    PackageManagement                   {Find-Package, Get-Package, Get-PackageProvider, Get-Pa...
Script     1.6.0      PowerShellGet                       {Install-Module, Find-Module, Save-Module, Update-Modul...

Environment data

> $PSVersionTable
Name                           Value
----                           -----
PSVersion                      6.1.0-preview.3
PSEdition                      Core
GitCommitId                    v6.1.0-preview.3
OS                             Linux 4.4.0-17134-Microsoft #112-Microsoft Thu Jun 07 22:57:00 PST 2018
Platform                       Unix
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0...}
PSRemotingProtocolVersion      2.3
SerializationVersion           1.1.0.1
WSManStackVersion              3.0

Copied from original issue: PowerShell/PowerShell#7264

[alastairs]

From @MaximoTrinidad on July 11, 2018 12:41

Hum!!

I don't think Azure is the correct module to load in PowerShell Core (WSL/Linux). You should use AzureRM.Netcore which is the one supported cross platform.

Azure module is only for Windows PowerShell.

:)

[alastairs]

I used Azure as an example; it’s also failing for the module I really want, InvokeBuild. (That said, Azure is a Script module, why wouldn’t it work?)

[alastairs]

From @MaximoTrinidad on July 11, 2018 12:58

First, I suggest to use AzureRM.Netcore. As using Azure module won't installed in WSL because is a Windows module.

Currently, your scenario can't be reproduce.

[alastairs]

Ok, as I said before, I used Azure as an example; my apologies for the red herring here @MaximoTrinidad.

InvokeBuild is the module I'm actually trying to install. On my machine, the module downloads, but does not appear to install correctly:

> Install-Module -Force InvokeBuild -Verbose -Scope CurrentUser
VERBOSE: Using the provider 'PowerShellGet' for searching packages.
VERBOSE: The -Repository parameter was not specified.  PowerShellGet will use all of the registered repositories.
VERBOSE: Getting the provider object for the PackageManagement Provider 'NuGet'.
VERBOSE: The specified Location is 'https://www.powershellgallery.com/api/v2/' and PackageManagementProvider is 'NuGet'.
VERBOSE: Searching repository 'https://www.powershellgallery.com/api/v2/FindPackagesById()?id='InvokeBuild'' for ''.
VERBOSE: Total package yield:'1' for the specified package 'InvokeBuild'.
VERBOSE: Performing the operation "Install-Module" on target "Version '5.4.1' of module 'InvokeBuild'".
VERBOSE: The installation scope is specified to be 'CurrentUser'.
VERBOSE: The specified module will be installed in '/home/alastair/.local/share/powershell/Modules'.
VERBOSE: The specified Location is 'NuGet' and PackageManagementProvider is 'NuGet'.
VERBOSE: Downloading module 'InvokeBuild' with version '5.4.1' from the repository 'https://www.powershellgallery.com/api/v2/'.
VERBOSE: Searching repository 'https://www.powershellgallery.com/api/v2/FindPackagesById()?id='InvokeBuild'' for ''.
VERBOSE: InstallPackage' - name='InvokeBuild', version='5.4.1',destination='/tmp/1697404623'
VERBOSE: DownloadPackage' - name='InvokeBuild', version='5.4.1',destination='/tmp/1697404623/InvokeBuild.5.4.1/InvokeBuild.5.4.1.nupkg', uri='https://www.powershellgallery.com/api/v2/package/InvokeBuild/5.4.1'
VERBOSE: Downloading 'https://www.powershellgallery.com/api/v2/package/InvokeBuild/5.4.1'.
VERBOSE: Completed downloading 'https://www.powershellgallery.com/api/v2/package/InvokeBuild/5.4.1'.
VERBOSE: Completed downloading 'InvokeBuild'.
VERBOSE: InstallPackageLocal' - name='InvokeBuild', version='5.4.1',destination='/tmp/1697404623'

I see your $PSVersionTable.OS is newer than mine. I'll try updating WSL and see if that makes a difference.

[alastairs]

No change in behaviour after an upgrade of WSL, but I'm still on an older build than yours @MaximoTrinidad:

> $PSVersionTable

Name                           Value
----                           -----
PSVersion                      6.1.0-preview.3
PSEdition                      Core
GitCommitId                    v6.1.0-preview.3
OS                             Linux 4.4.0-17134-Microsoft #137-Microsoft Thu Jun 14 18:46:00 PST 2018
Platform                       Unix
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0...}
PSRemotingProtocolVersion      2.3
SerializationVersion           1.1.0.1
WSManStackVersion              3.0

[alastairs]

From @MaximoTrinidad on July 11, 2018 13:41

Ah! That will do it, with all the different versions of Windows 10.
:(

Let me look at that module.

[alastairs]

From @MaximoTrinidad on July 11, 2018 13:56

@alastairs

Works on my system!

And, I also, have the non-Insider version:

[alastairs]

Ok, thanks for the update @MaximoTrinidad. I'm a bit at a loss of how to proceed from here; adding -Verbose to the installation attempt clearly indicates that the installation is not completing or, at least, seemingly silently failing. What avenues can I explore to troubleshoot this further?

[alastairs]

From @MaximoTrinidad on July 11, 2018 15:52

First! I have the tendency to first open PowerShell with 'sudo pwsh-preview' and then use the 'Install-Module ...". Are you using "sudo ..."?

:)

[alastairs]

Thanks @MaximoTrinidad 🙂 I've tried it with sudo pwsh-preview as well, same result...

[alastairs]

I've collected even more detailed logs from a run of Install-Module on my machine, in a sudo session. Here's the output, starting from the last line of the Verbose log output.

VERBOSE: InstallPackageLocal' - name='InvokeBuild', version='5.4.1',destination='/tmp/801868413'
DEBUG: 00:00:22.3447290 /tmp/801868413/InvokeBuild.5.4.1/InvokeBuild.5.4.1.nupkg
DEBUG: 00:00:23.0231080 Returning the call 'NuGetClient'::'InstallPackageLocal'.
DEBUG: 00:00:23.5740780 Returning the call 'NuGetClient'::'InstallSinglePackage'.
DEBUG: 00:00:23.6204030 PowerShell Script 'PSModule' Function 'Install-Package' returns null.
DEBUG: 00:00:23.6224580 Done calling powershell «Install-Package» «PSModule»

[alastairs]

From @mattpodwysocki on July 12, 2018 16:18

@alastairs can confirm as well with not only Ubuntu, but Debian and OpenSUSE as well.

> $PSVersionTable

Name                           Value
----                           -----
PSVersion                      6.1.0-preview.3
PSEdition                      Core
GitCommitId                    v6.1.0-preview.3
OS                             Linux 4.4.0-17713-Microsoft #1000-Microsoft Fri Jul 06 15:51:00 PST 2018
Platform                       Unix
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0...}
PSRemotingProtocolVersion      2.3
SerializationVersion           1.1.0.1
WSManStackVersion              3.0

Installing any module fails to properly install:

VERBOSE: The installation scope is specified to be 'CurrentUser'.
VERBOSE: The specified module will be installed in '/home/me/.local/share/powershell/Modules'.
VERBOSE: The specified Location is 'NuGet' and PackageManagementProvider is 'NuGet'.
VERBOSE: Downloading module 'posh-git' with version '0.7.3' from the repository 'https://www.powershellgallery.com/api/v2/'.
VERBOSE: Searching repository 'https://www.powershellgallery.com/api/v2/FindPackagesById()?id='posh-git'' for ''.
VERBOSE: InstallPackage' - name='posh-git', version='0.7.3',destination='/tmp/873133532'
VERBOSE: DownloadPackage' - name='posh-git', version='0.7.3',destination='/tmp/873133532/posh-git.0.7.3/posh-git.0.7.3.nupkg', uri='https://www.powershellgallery.com/api/v2/package/posh-git/0.7.3'
VERBOSE: Downloading 'https://www.powershellgallery.com/api/v2/package/posh-git/0.7.3'.
VERBOSE: Completed downloading 'https://www.powershellgallery.com/api/v2/package/posh-git/0.7.3'.
VERBOSE: Completed downloading 'posh-git'.
VERBOSE: InstallPackageLocal' - name='posh-git', version='0.7.3',destination='/tmp/873133532'

[alastairs]

From @MaximoTrinidad on July 12, 2018 16:34

Awesome! Nice to see someone reproduce the issue.
I don't know why I can't.

The only thing I'm suspecting is the use of the '-Score CurrentUser' as it may of more use in Windows.
Can some please share the exact one-liner to install it?

:)

[alastairs]

From @MaximoTrinidad on July 12, 2018 17:24

There's always the possibility that something did happened to the PowerShell Core installation.
I have unregister/register back to PSGallery repository and got different failure messages. But, I was able to recover and install any module.

Here's my installation Verbose:

PS /home/maxt> Install-Module -Name InvokeBuild -verbose -Scope CurrentUser -Force
VERBOSE: Using the provider 'PowerShellGet' for searching packages.
VERBOSE: The -Repository parameter was not specified.  PowerShellGet will use all of the registered repositories.
VERBOSE: Getting the provider object for the PackageManagement Provider 'NuGet'.
VERBOSE: The specified Location is 'https://www.powershellgallery.com/api/v2/' and PackageManagementProvider is 'NuGet'.
VERBOSE: Searching repository 'https://www.powershellgallery.com/api/v2/FindPackagesById()?id='InvokeBuild'' for ''.
VERBOSE: Total package yield:'1' for the specified package 'InvokeBuild'.
VERBOSE: Performing the operation "Install-Module" on target "Version '5.4.1' of module 'InvokeBuild'".
VERBOSE: The installation scope is specified to be 'CurrentUser'.
VERBOSE: The specified module will be installed in '/home/maxt/.local/share/powershell/Modules'.
VERBOSE: The specified Location is 'NuGet' and PackageManagementProvider is 'NuGet'.
VERBOSE: Downloading module 'InvokeBuild' with version '5.4.1' from the repository 'https://www.powershellgallery.com/api/v2/'.
VERBOSE: Searching repository 'https://www.powershellgallery.com/api/v2/FindPackagesById()?id='InvokeBuild'' for ''.
VERBOSE: InstallPackage' - name='InvokeBuild', version='5.4.1',destination='/tmp/655074114'
VERBOSE: DownloadPackage' - name='InvokeBuild', version='5.4.1',destination='/tmp/655074114/InvokeBuild/InvokeBuild.nupkg', uri='https://www.powershellgallery.com/api/v2/package/InvokeBuild/5.4.1'
VERBOSE: Downloading 'https://www.powershellgallery.com/api/v2/package/InvokeBuild/5.4.1'.
VERBOSE: Completed downloading 'https://www.powershellgallery.com/api/v2/package/InvokeBuild/5.4.1'.
VERBOSE: Completed downloading 'InvokeBuild'.
VERBOSE: InstallPackageLocal' - name='InvokeBuild', version='5.4.1',destination='/tmp/655074114'
VERBOSE: Module 'InvokeBuild' was installed successfully to path '/home/maxt/.local/share/powershell/Modules/InvokeBuild/5.4.1'.
PS /home/maxt>

Have this ever work before Preview.3?
Have you tried to reinstall PowerShell Core?

It has to be something with the installation.
Can you list the registered psrepository?

get-psrepository

[alastairs]

From @mattpodwysocki on July 13, 2018 3:54

@MaximoTrinidad Here is the table:

PS /home/me> Get-PsRepository

Name                      InstallationPolicy   SourceLocation
----                      ------------------   --------------
PSGallery                 Untrusted            https://www.powershellgallery.com/api/v2/