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
Running Find-Package -Name docker -ProviderName DockerMsftProvider works in a local powershell session. Running Find-Package PSWindowsUpdate -ProviderName PowershellGet works in a remote PS session. When I run the first command in the remote session, it produces:
VERBOSE: Using the provider 'DockerMsftProvider' for searching packages.
VERBOSE: Download size: 0.01MB
VERBOSE: Free space on the drive: 92728.79MB
VERBOSE: Downloading https://dockermsft.blob.core.windows.net/dockercontainer/DockerMsftIndex.json to
C:\Users\ADMINI~1\AppData\Local\Temp\DockerMsftProvider\DockerDefault_DockerSearchIndex.json
VERBOSE: About to download
WARNING: Cannot find path 'C:\Users\ADMINI~1\AppData\Local\Temp\DockerMsftProvider\DockerDefault_DockerSearchIndex.json' because it does not exist.
WARNING: Save-HTTPItem: Bits Transfer failed. Job State: ExitCode = -2147023651
Find-Package : No match was found for the specified search criteria and package name 'docker'. Try Get-PackageSource to see all
available registered package sources.
+ CategoryInfo : ObjectNotFound: (Microsoft.Power...ets.FindPackage:FindPackage) [Find-Package], Exception
+ FullyQualifiedErrorId : NoMatchFoundForCriteria,Microsoft.PowerShell.PackageManagement.Cmdlets.FindPackage
I can get the file using invoke-webrequest https://dockermsft.blob.core.windows.net/dockercontainer/DockerMsftIndex.json
Running
Find-Package -Name docker -ProviderName DockerMsftProvider
works in a local powershell session. RunningFind-Package PSWindowsUpdate -ProviderName PowershellGet
works in a remote PS session. When I run the first command in the remote session, it produces:I can get the file using
invoke-webrequest https://dockermsft.blob.core.windows.net/dockercontainer/DockerMsftIndex.json
Windows Server 2016, $PSVersionTable:
The text was updated successfully, but these errors were encountered: