[Enhancement]: Extending Testcontainers to support multiple container runtimes (Podman) #876
Open
5 of 10 tasks
Labels
enhancement
New feature or request
Problem
Since Testcontainers for Node has done an awesome job supporting multiple container runtimes (not just Docker), it makes perfect sense to continue this great work and look into implementing it for .NET. We can start by collecting a list of tasks, issues or incompabilities that are necessary to support other runtimes as well.
Docker.DotNet
'sExtractArchiveToContainerAsync(string, ContainerPathStatParameters, Stream, CancellationToken)
throwsSystem.Net.Sockets.SocketException : Connection reset by peer
.export TESTCONTAINERS_DOCKER_SOCKET_OVERRIDE=/var/run/docker.sock
fails:podman machine set --rootful=true
), the errors mentioned above do not occur. However, Testcontainers for .NET is either unable to establish a connection to the Resource Reaper or fails:TESTCONTAINERS_DOCKER_SOCKET_OVERRIDE=/var/run/docker.sock
andTESTCONTAINERS_RYUK_CONTAINER_PRIVILEGED=true
.K3sContainer
does not start (rancher/k3s:v1.26.2-k3s1
)LocalStackContainer
does not start (localstack/localstack:1.4
,localstack/localstack:2.0
)mtu
instead of thecom.docker.network.driver.mtu
key is used. Is themtu
a valid key for Docker (it is probably not that important since we only test if TC sets the property)?--hostname
,WithHostname(string)
), the ping commands fails withping: bad address '_container2'
.testcontainers-dotnet/tests/Testcontainers.Tests/Unit/Networks/TestcontainersNetworkTest.cs
Line 47 in f0fef3e
.DependsOn(new NetworkBuilder().Build())
works. The Podman "workaround" does not work with Docker.Solution
-
Benefit
-
Alternatives
-
Would you like to help contributing this enhancement?
Yes
The text was updated successfully, but these errors were encountered: