Creating container on Windows Server 2022 fails with transparent network - EOF: 125

[DobbyNator94]

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

Describe the issue
Hey,

we want to use use Docker CE / moby with Windows Server 2022 and use the transparent network:

https://learn.microsoft.com/en-us/virtualization/windowscontainers/quick-start/set-up-environment?tabs=dockerce

Problem is:

DockerDo : docker: error during connect: Post "http://%2F%2F.%2Fpipe%2Fdocker_engine/v1.47/containers/41d9a9b96cda56340
58f643bdd22bc0a5c4c6364d8399aaab19945c6f50773df/start": EOF.
ExitCode: 125

Scripts used to create container and cause the issue

New-BcContainer -accept_eula -accept_insiderEula -accept_outdated -artifactUrl https://bcartifacts-exdbf9fwegejdqak.b02.azurefd.net/onprem/25.1.25873.25900/de -isolation process -useSSL -additionalParameters "--net transparent"

Full output of scripts

PS C:\Windows\system32> New-BcContainer -accept_eula -accept_insiderEula -accept_outdated -artifactUrl https://bcartifacts-exdbf9fwegejdqak.b02.azurefd.net/onprem/25.1.25873.25900/de -isolation process -useSSL -additionalParameters "--net transparent"
BcContainerHelper is version 6.0.28
BcContainerHelper is running as administrator
HyperV is Disabled
Host is Microsoft Windows Server 2022 Datacenter - 10.0.20348.3091
UsePsSession is True
UsePwshForBc24 is True
UseWinRmSession is allow
UseSslForWinRmSession is True
Docker Client Version is 27.3.1
Docker Server Version is 27.3.1
Removing Desktop shortcuts
Fetching all docker images
Fetching all docker volumes
Using image mcr.microsoft.com/businesscentral:ltsc2022
Creating Container bcserver
Style: onprem
Multitenant: No
Version: 25.1.25873.25900
Platform: 25.0.25866.0
Generic Tag: 1.0.2.54
Container OS Version: 10.0.20348.3091 (ltsc2022)
Host OS Version: 10.0.20348.3091 (ltsc2022)
Using process isolation
Using locale de-DE
Disabling the standard eventlog dump to container log every 2 seconds (use -dumpEventLog to enable)
Additional Parameters:
--net transparent
--expose 5986
Files in C:\ProgramData\BcContainerHelper\Extensions\bcserver\my:

AdditionalOutput.ps1
AdditionalSetup.ps1
HelperFunctions.ps1
MainLoop.ps1
SetupVariables.ps1
updatecontainerhosts.ps1
Creating container bcserver from image mcr.microsoft.com/businesscentral:ltsc2022
8101aed178b21f53f4c2c158ef780b00325218ef53003809c4cb249faac740de
New-BcContainer Telemetry Correlation Id: 467c915d-e0b8-4139-95db-c0f1f3bacaa3
DockerDo : docker: error during connect: Post "http://%2F%2F.%2Fpipe%2Fdocker_engine/v1.47/containers/8101aed178b21f53f
4c2c158ef780b00325218ef53003809c4cb249faac740de/start": EOF.
ExitCode: 125
Commandline: docker run --volume "c:\bcartifacts.cache:c:\dl" --label nav= --env isBcSandbox=N --label
version=25.1.25873.25900 --label platform=25.0.25866.0 --label country=de --env
artifactUrl=https://bcartifacts-exdbf9fwegejdqak.b02.azurefd.net/onprem/25.1.25873.25900/de --env licenseFile=""
--name bcserver --hostname bcserver --env auth=Windows --env username="dobbermann" --env ExitOnError=N --env
locale=de-DE --env databaseServer="" --env databaseInstance="" --volume
"C:\ProgramData\BcContainerHelper:C:\ProgramData\BcContainerHelper" --volume
"C:\ProgramData\BcContainerHelper\Extensions\bcserver\my:C:\Run\my" --isolation process --restart unless-stopped --env
filesOnly=False --env enableApiServices=Y --env useSSL=Y --env securePassword=
--env passwordKeyFile="c:\run\my\aes.key" --env removePasswordKeyFile=Y --net transparent --expose 5986 --env
accept_eula=Y --env accept_outdated=Y --detach mcr.microsoft.com/businesscentral:ltsc2022
In C:\Program Files\WindowsPowerShell\Modules\BcContainerHelper\6.0.28\ContainerHandling\New-NavContainer.ps1:1859
Zeichen:15
... if (!(DockerDo -accept_eula -accept_outdated:$accept_outdated - ...
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
CategoryInfo : NotSpecified: (:) [Write-Error], WriteErrorException
FullyQualifiedErrorId : Microsoft.PowerShell.Commands.WriteErrorException,DockerDo

Additional context

• It does not work on two corporate servers in our network. The third is working fine with a transparent network,

[freddydk]

Whenever I see an ExitCode 125 - the solution is normally to do a deep cleanup of the docker file system and retry.
Maybe this can help: https://freddysblog.com/2018/12/11/clean-up-after-yourself-docker-your-mom-isnt-here/