testcontainers-dotnet: InvalidOperationException `cannot hijack chunked ... stream` (Rancher Desktop, Docker Desktop 4.10.0)

Quick update because I know a couple of devs waiting for a fix. We’re trying to contact the maintainers. If that somehow won’t work we’ll fork and fix it.

Same on Docker Desktop for Mac (4.10.0) it seems, downgrading to 4.9.1 makes the error go away.

System.AggregateException : One or more errors occurred. (cannot hijack chunked or content length stream) (cannot hijack chunked or content length stream)
---- System.InvalidOperationException : cannot hijack chunked or content length stream
---- System.InvalidOperationException : cannot hijack chunked or content length stream
 Stack Trace:
----- Inner Stack Trace #1 (System.InvalidOperationException) -----
  at [Microsoft.Net](http://microsoft.net/).Http.Client.HttpConnectionResponseContent.HijackStream()
  at Docker.DotNet.DockerClient.MakeRequestForHijackedStreamAsync(IEnumerable`1 errorHandlers, HttpMethod method, String path, IQueryString queryString, IRequestContent body, IDictionary`2 headers, TimeSpan timeout, CancellationToken cancellationToken)
  at Docker.DotNet.ContainerOperations.AttachContainerAsync(String id, Boolean tty, ContainerAttachParameters parameters, CancellationToken cancellationToken)
  at DotNet.Testcontainers.Clients.DockerContainerOperations.AttachAsync(String id, IOutputConsumer outputConsumer, CancellationToken ct)
  at DotNet.Testcontainers.Containers.Modules.TestcontainersContainer.Start(String id, CancellationToken ct)
  at DotNet.Testcontainers.Containers.Modules.TestcontainersContainer.StartAsync(CancellationToken ct)```

I’ve emailed the @dotnet-foundation and asked if they can help us, or if I can get access to the repository. I prefer a fix in the upstream. A fork should be the last option.

Awesome 🥳 I’ll publish a release version later that day. Thanks for your response.

Just to update the group here – the maintainer responded and Docker.Dotnet has a new release that includes @HofmeisterAn’s fix.

So I think as soon as we get a new release of testcontainers-dotnet with the updated Docker.Dotnet dependency, we should be good.

I can confirm. It’s broken for Docker Desktop for Windows (4.10.0) too. We need a fix in https://github.com/dotnet/Docker.DotNet/issues/554.

@HofmeisterAn just coming across this. I also reached out to the .NET Foundation Maintainers committee on the Discord & Slack to see if pinging there might help move it along.

In a way, I’m relieved – was testing Testcontainers for the first time (LOVE the idea!) and thought I’d done something wrong 😅

Getting this bug as well after updating to 4.10.