Closed billykwooten closed 4 years ago
Should be fixed whith #29
A temporary solution is to add Enter-PSSession -ComputerName $env:COMPUTERNAME
at the beginning of the script (see this comment).
BITS Transfer has now been removed from the provider. If you install DockerMsftProvider from the PowerShell Gallery, you should get version 1.0.0.3 which has this fix. You can also use Update-Module -Name "DockerMsftProvider"
to update your provider.
@enderb-ms Sorry to jump in here, it seems I'm getting an issue related to this:
Am I doing anything wrong given this provider fix?
I'm seeing the same. I installed version 1.0.0.3 yesterday. nstall-Package : The specified module 'C:\Program Files\WindowsPowerShell\Modules\DockerMsftProvider\1.0.0.3\SaveHTTPItemUsingBITS.psm1' was not loaded because no valid module file was found in any module directory.
@tomasquith and @Skimo0412 thank you for reporting those. That error has been fixed with PR #38 and the fix has been pushed to the PS Gallery
Thanks @enderb-ms, I managed to prove this on Friday - cheers for the quick fix! :)
Replicate Issue
Environment
Windows Server 2016 VMWare ESXi 6.5
Issue Code Block