Unable to open docker hosted BC client in any browser.

[DomKaz]

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

Describe the issue
As of update to Windows 11 24H2, unable to open local docker hosted BC client in any browser.
Using bc container wizard to create my containers.

• Affects old and newly created containers.
• The containers are running and can be pinged, but any attept to open BC via browser just loads infinately.
• I can download symbols from the container.
• The hosts file is configured fine, connecting via http://localip/bc/ doesnt work either.
• There is no HTTP response from the bc client when trying to connect to it.
• Restarting IIS or BC service within the container does not help.

I had this update happen 2 weeks ago which caused exactly the same issue so I reverted it. But now the update is forced by company policy. I have a colleague on a different device with the same issue.

EDIT:
My colleague has had this issue for ~2/3 weeks himself, he did not roll back an update. It might not be specifically the 24H2 update as he's still on Win11 23H2, but the issue started occuring immediately after windows updates were installed.

Scripts used to create container and cause the issue
Example script I tried this morning. Its pretty much default container wizard, the only non-default options being gb location and multitenant being set to false. Seeing how the issue affecs old and new containers, this probably isnt of use.

$containerName = 'bc25-sandbox'
$credential = Get-Credential -Message 'Using UserPassword authentication. Please enter credentials for the container.'
$auth = 'UserPassword'
$artifactUrl = Get-BcArtifactUrl -type 'Sandbox' -country 'gb' -select 'Latest'
New-BcContainer `
    -accept_eula `
    -containerName $containerName `
    -credential $credential `
    -auth $auth `
    -artifactUrl $artifactUrl `
    -multitenant:$false `
    -assignPremiumPlan `
    -memoryLimit 8G `
    -updateHosts

Full output of scripts

NavContainerHelper is version 6.0.22
NavContainerHelper is running as administrator
Host is Microsoft Windows 11 Enterprise - 10.0.26100 Build 26100
Docker version 27.2.0, build 3ab4256
...

Screenshots



An attept to download symbols from one of my old containers is succeeding.

[SShadowS]

Checked your eventlog?
Let me guess, you also get entries like this:
exec's CreateProcess() failed [namespace=moby container=7283b26f5ca5e05e47e8e50d20e3995a109f73c5f2dcd2cee147a64c701b2e73 exec=9cc6530134e6f7adcb9f5478dc7dfcd03bc0deb9795109352093201b71a33427 module=libcontainerd error=container 7283b26f5ca5e05e47e8e50d20e3995a109f73c5f2dcd2cee147a64c701b2e73 encountered an error during hcs::System::CreateProcess: cmd.exe /C "ECHO 192.168.2.99 host.docker.internal >> %systemroot%\system32\drivers\etc\hosts & ECHO 192.168.2.99 gateway.docker.internal >> %systemroot%\system32\drivers\etc\hosts": failure in a Windows system call: The user name or password is incorrect. (0x52e)]

[freddydk]

One of my colleagues observed the same when updating to Windows 11 24H2 - mine worked fine, because I switched to use HyperV isolation a while back (due to performance reasons). When I switched to Process isolation - it also failed on my machine

Another benefit of using HyperV isolation is that the container creation time is cut in half and the container runs faster.

The latest BcContainerHelper version will default to HyperV isolation when running Windows 11 24H2 as this fixes the problem.

[freddydk]

See also #3730 and maybe even #2986

[fvet]

I encountered the same this week and can confirm that switching from process isolation to HyperV isolation fixed the issue!