microsoft / navcontainerhelper

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

CAN'T CREATE A DOCKER CONTAINER #3225

Closed BotanAbabakar007 closed 9 months ago

BotanAbabakar007 commented 11 months ago

PLEASE DO NOT INCLUDE ANY PASSWORDS OR TOKENS IN YOUR ISSUE!!!

Describe the issue I have been able to create containers before, but now i get the same error when i try to create a container.

Scripts used to create container and cause the issue

PS C:\Users\bab> cd "C:\Users\bab\Documents\AL\EQM365\PowerShell_Scripts"                                                                   PS C:\Users\bab\Documents\AL\EQM365\PowerShell_Scripts> .\CreateBcContainer.ps1
Latest BcContainerHelper is installed.
BcContainerHelper version 6.0.0
BC.HelperFunctions emits usage statistics telemetry to Microsoft

Choose a localization ( W1, NO, DK or US ): NO

Enter Container Name: UCOARM21

Full output of scripts

Downloading EQM license to C:\Users\bab\Documents\AL\EQM365\PowerShell_Scripts\eqm_365_license.flf
EQM license downloaded.

BcContainerHelper is version 6.0.0
BcContainerHelper is running as administrator
HyperV is Enabled
UsePsSession is True
Host is Microsoft Windows 11 Pro - 10.0.22631.2506
Docker Client Version is 24.0.6
Docker Server Version is 24.0.6
Removing Desktop shortcuts
Fetching all docker images
Fetching all docker volumes
Using image mcr.microsoft.com/businesscentral:10.0.20348.2031
Creating Container UCOARM21
Style: onprem
Multitenant: No
Version: 21.6.54874.0
Platform: 21.0.54828.0
Generic Tag: 1.0.2.14
Container OS Version: 10.0.20348.2031 (ltsc2022)
Host OS Version: 10.0.22631.2506 (Unknown/Insider build)
Using process isolation
Using locale nb-NO
Disabling the standard eventlog dump to container log every 2 seconds (use -dumpEventLog to enable)
Using license file C:\Users\bab\Documents\AL\EQM365\PowerShell_Scripts\eqm_365_license.flf
Files in C:\ProgramData\BcContainerHelper\Extensions\UCOARM21\my:
- AdditionalOutput.ps1
- license.flf
- MainLoop.ps1
- SetupVariables.ps1
- updatehosts.ps1
Creating container UCOARM21 from image mcr.microsoft.com/businesscentral:10.0.20348.2031
New-BCContainer Telemetry Correlation Id: 2a72e496-329f-4b42-b264-10d612d2e3d9
docker: Error response from daemon: hcsshim::ExpandScratchSize failed in Win32: The semaphore timeout period has expired. (0x79).
See 'docker run --help'.
ExitCode: 125
Commandline: docker run --volume "c:\bcartifacts.cache:c:\dl" --label nav= --env isBcSandbox=N --label version=21.6.54874.0 --label platform=21.0.54828.0 --label country=no --env artifactUrl=https://bcartifacts.azureedge.net/onprem/21.6.54874.0/no --env licenseFile="c:\run\my\license.flf" --name UCOARM21 --hostname UCOARM21 --env auth=NavUserPassword --env username="admin" --env ExitOnError=N --env locale=nb-NO --env databaseServer="" --env databaseInstance="" --volume "C:\ProgramData\BcContainerHelper:C:\ProgramData\BcContainerHelper" --volume "C:\ProgramData\BcContainerHelper\Extensions\UCOARM21\my:C:\Run\my" --isolation process --restart unless-stopped --env filesOnly=False --env enableApiServices=Y --env useSSL=N --volume "c:\windows\system32\drivers\etc:C:\driversetc" --env securePassword=76492d1116743f0423413b16050a5345MgB8AFEAeAA2AHMAZwB0AGwAQwBlAGgAYgBTAEkANwBRAG0ARAA1AHIASQAwAGcAPQA9AHwAMAA3ADIAOQBiAGEAZgBiADEAZgBiADAAZQA0ADMAMwAwADQAMQAwAGUANwA3AGUANgAwADMAYwA4ADkAOABjAA== --env passwordKeyFile="c:\run\my\aes.key" --env removePasswordKeyFile=Y --env accept_eula=Y --env accept_outdated=Y --detach mcr.microsoft.com/businesscentral:10.0.20348.2031

Screenshots CantCreateContainer

BotanAbabakar007 commented 11 months ago

image

freddydk commented 11 months ago

I haven't seen this before, but I would say that it looks like a problem on your computer. If you have enought memory and disk space available, you could try the cleanup process described here: https://freddysblog.com/2018/12/11/clean-up-after-yourself-docker-your-mom-isnt-here/ or a re-install of docker and/or OS.