testcontainers/Docker.DotNet

AI Summary: The issue is that Testcontainers version 4.5.0 and 4.6.0 fail to connect to a Docker daemon running within Rancher Desktop on Windows, throwing a `System.InvalidOperationException` related to hijacking streams. The problem only manifests on the developer's local machine and not in a CI environment. Debugging requires investigating the interaction between Testcontainers, Docker.DotNet (the underlying Docker client library), and the Rancher Desktop environment, potentially involving network configuration, Docker daemon settings, or compatibility issues between library versions and the Rancher Desktop Docker implementation.

AI Summary: Investigate how Docker.DotNet manages connections to the Docker daemon, specifically focusing on named pipe connections. The goal is to determine if connection reuse is implemented efficiently and to identify potential causes of timeouts observed when making many parallel API calls, particularly with Podman Desktop for Windows. This involves analyzing the Docker.DotNet source code and potentially implementing improvements to enhance connection management and reuse.

AI Summary: The issue is a `System.InvalidOperationException` occurring in Testcontainers for .NET when starting a MSSQL container on Windows using Rancher Desktop. The root cause seems to be within the `Docker.DotNet` library's handling of streamed responses from the Docker daemon, possibly due to an incompatibility introduced by a recent Rancher Desktop update. The task involves debugging the interaction between Testcontainers, `Docker.DotNet`, and the Docker daemon (version 27.3.1) to identify and fix the stream hijacking problem. This likely requires examining the `Docker.DotNet` source code, network traffic, and potentially updating the library to handle the specific response format from the Docker daemon.