Describe the issue
When calling UploadImportAndApply-ConfigPackageInBcContainer (in either a local context or in an Azure DevOps pipeline on a VM build using the same packer definition as the Microsoft build agents), the following error occurs:
operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again.
At C:\Program Files\WindowsPowerShell\Modules\BcContainerHelper\5.0.1\ConfigPackageHandling\UploadImportAndApply-ConfigPackageInBcContainer.ps1:44 char:32
+ ... $packageInfo = Get-PackageInfoFromRapidStartFile $config ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : ObjectNotFound: (Get-PackageInfoFromRapidStartFile:String) [], ParentContainsErrorRecordException
+ FullyQualifiedErrorId : CommandNotFoundException
Scripts used to create container and cause the issue
Has been occuring since the module updated to 5.0.1 (but possibly earlier as we weren't running these containers for a few weeks due to a different blocker)
Describe the issue When calling
UploadImportAndApply-ConfigPackageInBcContainer
(in either a local context or in an Azure DevOps pipeline on a VM build using the same packer definition as the Microsoft build agents), the following error occurs:Scripts used to create container and cause the issue
(Local-variables is uninteresting - but the relevant values:
Full output of scripts
Additional context