Testcontainers version
4.4.0
Using the latest Testcontainers version?
Yes
Host OS
Windows
Host arch
x64
.NET version
9.0.201
Docker version
Docker version 27.5.1, build 9f9e405
Docker info
Server Version: 27.5.1
Storage Driver: overlay2
Backing Filesystem: extfs
Supports d_type: true
Using metacopy: false
Native Overlay Diff: true
userxattr: false
Logging Driver: json-file
Cgroup Driver: cgroupfs
Cgroup Version: 1
Plugins:
Volume: local
Network: bridge host ipvlan macvlan null overlay
Log: awslogs fluentd gcplogs gelf journald json-file local splunk syslog
CDI spec directories:
/etc/cdi
/var/run/cdi
Swarm: inactive
Runtimes: nvidia runc io.containerd.runc.v2
Default Runtime: runc
Init Binary: docker-init
containerd version: bcc810d6b9066471b0b6fa75f557a15a1cbf31bb
runc version: v1.1.12-0-g51d5e946
init version: de40ad0
Security Options:
seccomp
Profile: unconfined
Kernel Version: 5.15.167.4-microsoft-standard-WSL2
Operating System: Docker Desktop
OSType: linux
Architecture: x86_64
CPUs: 32
Total Memory: 62.73GiB
Name: docker-desktop
ID: 30beda7b-3cef-4d79-b91e-9571b18fde37
Docker Root Dir: /var/lib/docker
Debug Mode: false
HTTP Proxy: http.docker.internal:3128
HTTPS Proxy: http.docker.internal:3128
No Proxy: hubproxy.docker.internal
Labels:
com.docker.desktop.address=npipe://\\.\pipe\docker_cli
Experimental: false
Live Restore Enabled: false
What happened?
Azurite hangs on start when configured with WithReuse(true) when it's already started.
It seems to be caused by the wait strategy.
Is the wait strategy necessary? I ran some basic tests, and I'm able to connect just fine without it.
Relevant log output
Additional information
No response
Testcontainers version
4.4.0
Using the latest Testcontainers version?
Yes
Host OS
Windows
Host arch
x64
.NET version
9.0.201
Docker version
Docker info
What happened?
Azurite hangs on start when configured with
WithReuse(true)when it's already started.It seems to be caused by the wait strategy.
Is the wait strategy necessary? I ran some basic tests, and I'm able to connect just fine without it.
Relevant log output
Additional information
No response