testcontainers/testcontainers-java

Unable to run Testcontainers on Windows Server 2019 (LinuxKit installed, LCOW)

Open

#2,960 opened on Jul 1, 2020

View on GitHub
 (23 comments) (0 reactions) (0 assignees)Java (7,535 stars) (1,588 forks)batch import
client/docker-for-windowshelp wantedos/windowsresolution/acknowledged

Description

Unable to run containers from testcontainer in Windows Server 2019 (LinuxKit installed). This link https://www.testcontainers.org/supported_docker_environment/ mentions that LCOW is supported. Able to run a linux container without any issue from Docker CLI.

Facing issues only when tried to run a container from testcontainer.

Error logs as below:

2020-07-01 20:12:59.342 ERROR 4936 --- [           main] o.t.d.DockerClientProviderStrategy       : Could not find a valid Docker environment. Please check configuration. Attempted configurations were:
2020-07-01 20:12:59.342 ERROR 4936 --- [           main] o.t.d.DockerClientProviderStrategy       :     NpipeSocketClientProviderStrategy: failed with exception InvalidConfigurationException (ping failed). Root cause TimeoutException (null)
2020-07-01 20:12:59.342 ERROR 4936 --- [           main] o.t.d.DockerClientProviderStrategy       :     WindowsClientProviderStrategy: failed with exception TimeoutException (org.rnorth.ducttape.TimeoutException: java.util.concurrent.TimeoutException). Root cause TimeoutException (null)
2020-07-01 20:12:59.342 ERROR 4936 --- [           main] o.t.d.DockerClientProviderStrategy       : As no valid configuration was found, execution cannot continue

Docker Info as below:

Client: Debug Mode: false Plugins: cluster: Manage Docker clusters (Docker Inc., v1.2.0) Server: Containers: 4 Running: 1 Paused: 0 Stopped: 3 Images: 6 Server Version: 19.03.5 Storage Driver: windowsfilter (windows) lcow (linux) Windows: LCOW: Logging Driver: json-file Plugins: Volume: local Network: ics internal l2bridge l2tunnel nat null overlay private transparent Log: awslogs etwlogs fluentd gcplogs gelf json-file local logentries splunk syslog Swarm: inactive Default Isolation: process Kernel Version: 10.0 17763 (17763.1.amd64fre.rs5_release.180914-1434) Operating System: Windows Server 2019 Standard Version 1809 (OS Build 17763.1294) OSType: windows Architecture: x86_64 CPUs: 4 Total Memory: 16GiB Name: DHUBAS204 ID: ZWHK:7HAM:2IKC:YTDS:RD7L:P2V6:6ECL:A2I3:X6T2:2N33:3KSQ:ZX24 Docker Root Dir: C:\ProgramData\docker Debug Mode: true File Descriptors: -1 Goroutines: 31 System Time: 2020-07-01T14:00:30.2657542+10:00 EventsListeners: 0 Registry: https://index.docker.io/v1/ Labels: Experimental: true Insecure Registries: registry-1.docker.io 127.0.0.0/8 Registry Mirrors: Live Restore Enabled: false

Contributor guide

Tech stack
javadocker
Domain
backendtestingdevops
Issue type
bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
mostly clear
Prerequisites
JavaDockerTestcontainers
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
20
Research direction
Investigate Testcontainers' Docker client provider strategies for Windows, specifically NpipeSocketClientProviderStrategy and WindowsClientProviderStrategy, which fail to connect to Docker despite Docker CLI working. Check Testcontainers documentation on LCOW support and examine any configuration differences between Docker CLI and Testcontainers. Look for related issues or PRs in the repository addressing Windows Server 2019 or LCOW compatibility.