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

[DobbyNator94]

Describe the bug
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

To Reproduce

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

Expected behavior
A functional container with a transparent network. What does EOF 125 mean? If there is a better output, maybe I can fix it by myself?

Configuration:

Client:
Version: 27.3.1
API version: 1.47
Go version: go1.22.7
Git commit: ce12230
Built: Fri Sep 20 11:42:27 2024
OS/Arch: windows/amd64
Context: default

Server: Docker Engine - Community
Engine:
Version: 27.3.1
API version: 1.47 (minimum version 1.24)
Go version: go1.22.7
Git commit: 41ca978
Built: Fri Sep 20 11:40:58 2024
OS/Arch: windows/amd64
Experimental: false

Containers: 1
Running: 1
Paused: 0
Stopped: 0
Images: 4
Server Version: 27.3.1
Storage Driver: windowsfilter
Windows:
Logging Driver: json-file
Plugins:
Volume: local
Network: ics internal l2bridge l2tunnel nat null overlay private transparent
Log: awslogs etwlogs fluentd gcplogs gelf json-file local splunk syslog
Swarm: inactive
Default Isolation: process
Kernel Version: 10.0 20348 (20348.1.amd64fre.fe_release.210507-1500)
Operating System: Microsoft Windows Server Version 21H2 (OS Build 20348.3091)
OSType: windows
Architecture: x86_64
CPUs: 8
Total Memory: 64GiB
Name: bre-dev-con03
ID: 91f7e039-75c2-4c5c-a5c9-3b67b37086ca
Docker Root Dir: C:\ProgramData\docker
Debug Mode: false
Experimental: false
Insecure Registries:
127.0.0.0/8
Live Restore Enabled: false
Product License: Community Engine

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

[github-actions]

Thank you for creating an Issue. Please note that GitHub is not an official channel for Microsoft support requests. To create an official support request, please open a ticket here. Microsoft and the GitHub Community strive to provide a best effort in answering questions and supporting Issues on GitHub.

[adrianm-msft]

@DobbyNator94 exit code 125 is a Docker error indicating that the Docker command itself failed, possibly due to incorrect options or an issue with Docker’s internals.

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

Are you executing the same command on all three servers? I'm curious if there are any environmental differences between the servers where it succeeded and where it failed.

[DobbyNator94]

I've also made an issue on the Moby team, link down here:

moby/moby#49334

There is a lot more debug information. Would be great @adrianm-msft , if you can take a look.
I'm not in our IT department, I don't have access to all VMware hypervisor and the portgroup settings, so I must take it for granted what information I am getting.

It doesn't matter if I make it via NavContainerHelper or normal docker run with a simple windowservernanoserver image. If I choose transparent network docker can't attach to container and it ends there.

[adrianm-msft]

@DobbyNator94 what are the repro steps using the normal Docker run commands?

[DobbyNator94]

@adrianm-msft everything is there in the moby/moby#49334

[adrianm-msft]

@DobbyNator94 which Docker command did you use to create the transparent network? I couldn't find it in moby/moby#49334. It looks like you got l2bridge working, though. I'm curious why you initially opted for a transparent network.

[DobbyNator94]

@adrianm-msft, because transparent network is not working and I need an alternative. If you have any input to make the transparent work, I‘m glad to hear it.