- Docker for Windows needs to be installed
- Docker version 17.06 is confirmed to work on Windows 10 with Hyper-V.
- Testcontainers supports communication with Docker on Docker for Windows using named pipes.
The following features are not available or do not work correctly so make sure you do not use them or use them with caution. The list may not be complete.
Testcontainers is not regularly tested on Windows, so please consider it to be at an beta level of readiness.
If you wish to use Testcontainers on Windows, please confirm that it works correctly for you before investing significant effort.
- MySQL server prevents custom configuration file (ini-script) from being loaded due to security measures (link to feature description)
Windows Container on Windows (WCOW)
- WCOW is currently not supported, since Testcontainers uses auxiliary Linux containers for certain tasks and Docker for Windows does not support hybrid engine mode at the time of writing.
Windows Subsystem for Linux
Testcontainers supports communicating with Docker for Windows within the Windows Subsystem for Linux (WSL). The following additional configurations steps are required:
Expose the Docker for Windows daemon on tcp port
2375without TLS. (Right-click the Docker for Windows icon on the task bar, click setting and go to
DOCKER_HOSTenvironment variable inside the WSL shell to
tcp://localhost:2375. It is recommended to add this to your
~/.bashrcfile, so it’s available every time you open your terminal.
Optional - Only if volumes are required:
Inside the WSL shell, modify the
/ect/wsl.conffile to mount the Windows drives on
/instead of on
/mnt/. (Reboot required after this step).
Remember to share the drives, on which you will store your volumes, with Docker for Windows. (Right-click the Docker for Windows icon on the task bar, click setting and go to
More information about running Docker within the WSL can be found here.
Please report any issues with the Windows build of Testcontainers here and be sure to note that you are using this on Windows.