Hi Freddy,
Have such issue when trying to run New-BcContainer
BcContainerHelper version 2.0.4

The script:
docker login $bcinsiderAzurecrIo -u $bcinsiderUser -p $bcinsiderPass
New-BcContainer `
-accept_eula `
-containerName $containerName `
-credential $credential `
-auth $auth `
-artifactUrl $artifactUrl `
-multitenant:$false `
-includeTestToolkit `
-includeTestLibrariesOnly `
-assignPremiumPlan `
-licenseFile $licenseFileUri `
-memoryLimit 6G `
-doNotExportObjectsToText `
-updateHosts `
-EnableTaskScheduler:$false
Setup-BcContainerTestUsers -containerName $containerName -Password $credential.Password -credential $credential
What could be the reason?
Looks like setup-bccontainertestusers doesn't work with 18.0
Will look at that.
BTW - you don't need the docker login anymore - our images are public - artifacts are secured by a sas token, but that is not docker login
Yeah, I will fix the bug, but in the meantime, you can run this as the last line:
Setup-BcContainerTestUsers -containerName $containerName -Password $credential.Password -credential $credential -createTestUsersAppUrl "https://businesscentralapps.azureedge.net/createtestusers/latest/apps.zip"
Fix shipped in 2.0.5