microsoft / navcontainerhelper

Official Microsoft repository for BcContainerHelper, a PowerShell module, which makes it easier to work with Business Central Containers on Docker.
MIT License
383 stars 247 forks source link

The system cannot find the file specified. ExitCode: 127 #3531

Closed jstokesdubose closed 5 months ago

jstokesdubose commented 5 months ago

The following is a recurring error message that I cannot unravel. Please help. I have replaced username, password, and some other sensitive information with $slugs or .

Docker Client Version is 26.0.0 BcContainerHelper version is 6.0.17

I am creating this container inside a VMWare VM. I have done this fifty times. I have never gotten this error before.

$artifactUrl = Get-BCArtifactUrl -country us -select Latest

$imageName = 'mcr.microsoft.com/businesscentral/sandbox:us'

$licenseFile = $license $ContainerName = $containername # should be the same as the ServerName in launch.json for the app $UserName = $myname $Password = ConvertTo-SecureString $mypassword -AsPlainText -Force $Credential = New-Object System.Management.Automation.PSCredential ($UserName, $Password)

New-BCContainer -accept_eula -containerName $ContainerName -artifactUrl $artifactUrl -licenseFile $licenseFile -auth NavUserPassword -updateHosts -Credential $Credential -isolation hyperv ` -includeTestToolkit

BcContainerHelper version 6.0.17 WinRM service is not running, will not try to use WinRM sessions BC.HelperFunctions emits usage statistics telemetry to Microsoft Running on Windows, PowerShell 5.1.19041.4291 BcContainerHelper is version 6.0.17 BcContainerHelper is running as administrator HyperV is Enabled Host is Microsoft Windows 10 Pro - 10.0.19045.4291 UsePsSession is True UsePwshForBc24 is True UseWinRmSession is never UseSslForWinRmSession is True Docker Client Version is 26.0.0 Docker Server Version is 26.0.0 Removing entries from hosts Removing from container hosts file Removing -* from container hosts file Removing Desktop shortcuts Removing C:\ProgramData\BcContainerHelper\Extensions\ Fetching all docker images Fetching all docker volumes Using image mcr.microsoft.com/businesscentral:ltsc2019 Creating Container Style: sandbox Multitenant: Yes Version: 24.0.16410.19164 Platform: 24.0.19145.0 Generic Tag: 1.0.2.20 Container OS Version: 10.0.17763.5696 (ltsc2019) Host OS Version: 10.0.19045.4291 (22H2) Using hyperv isolation Using locale en-US Disabling the standard eventlog dump to container log every 2 seconds (use -dumpEventLog to enable) Using license file C:\Licenses\2024v24.bclicense Files in C:\ProgramData\BcContainerHelper\Extensions\\my:

jstokesdubose commented 5 months ago

Reinstalling Docker under WSL (twice) and multiple reboots allowed me to run new-bccontainer. Although it showed errors at the end and hung, another reboot of the system was performed. Docker did not start without errors, though. After two more system reboots, it did.

I consider Docker on Windows an unstable platform.