Unable to run Testcontainers on Windows Server 2019 (LinuxKit installed, LCOW) #2960
Comments
|
Thanks for bringing this to our attention. From the error log, we can infer, that Testcontainers was not able to communicate with the Docker daemon over the named pipe. From looking into the Docker docs, I wonder if running this PowerShell command would give us further insights: |
|
@kiview Thank you very much for your response. Below is the error I receive on executing that command in powershell: Also to note: I'm able to run testcontainer successfully with named pipe in my laptop with Windows installed. The failure is only in Windows server |
|
TBH no idea if the URL is correct or not, this was simply copied from Docker Enterprise docs. It also does not work on my Windows machine. Maybe we can find another way to investigate if the named pipe is accessible. I found another blog post, which might be relevant to the problem. It seems, that under Windows server, the named pipe is only accessible with elevated permissions. Reading into this, I assume there is nothing Testcontainers can do here. |
|
Thanks @kiview. It really helped to progress to next step. When running with Admin privileges, it fails with the below error in testcontainer: windows is currently not supported. Additional info:-
|
|
So, Testcontainers sees the environment as a Windows container environment, I will need to investigate this in the sources. Maybe the check is just overly cautious abd it would work from a technical standpoint. |
|
Thanks for looking into this @kiview . Will wait for your feedback |
|
Ok, I found the problematic part in our code. We check the OS type as reported by the Docker client: And your Docker daemon would indeed respond with Therefore, I pushed an experimental branch which removed this strict check, could you try it out in your environment? You can consume it using Jitpack. |
|
Thanks @kiview. Apologies for the delay as I was behind a corporate proxy. Needed to sort that out first to use jitpack. Your solution helped me progress further but getting errors with volume mount while starting a localstack container. I noticed few previously reported issues in testcontainer around volume mount but couldn't get it to work. Could you please help @kiview StackTrace:- |
|
@ssureshraja when pasting stacktraces, please use triple backtick ( |
|
The first error probably happens when we try to run Ryuk and mount the Docker socket. So there is no Docker socket to be mounted, which is very different to how Docker for Windows works on Windows 10 Pro (where Docker is running in a Linux VM and therefore can mount the socket). You can disable Ryuk, but I expect you to run in another problem afterwards. But maybe give it a try. TBH, because of lack of resources and testing environment, I currently see the only solution in changing the docs to highlight, that Windows Server is currently not supported. |
kiview
changed the title
|
Thanks for all your help @kiview . For now, I'll switch to other option |
|
Hey @kiview & @bsideup - good to somehow meet again ✌️ It's been far to long... Remember the great testcontainers talk from @bsideup at JUG Thüringen in Gotha! We're currently setting up a Windows Build for our https://github.com/codecentric/spring-boot-admin project, since we get more and more Windows related bugs and wanted to have a build for that. Using GitHub Actions together with the From the state of this issue I assume that there's no big progress with this problem, right? I just read the "blind spot" thing:
With GitHub Actions it would be an option to eliminate the blind spot 😃 (see https://docs.github.com/en/actions/reference/specifications-for-github-hosted-runners#supported-runners-and-hardware-resources). |
…since Windows Server 2019 isn't supported right now by Testcontainers testcontainers/testcontainers-java#2960).
|
Hi @jonashackt! Good to "see" you too :) The problem with FYI we do have a Windows CI node running now. It runs Docker for Windows (in Linux mode) and we test every commit in our main branch before we cut a release :) |
|
Ah really nice, I tried to find a CI configuration (Circle, GitHub Actions, Travis..) in testcontainers root but wasn't able to find a Windows config. Could you give me a hint? |
|
@jonashackt we use Azure Pipelines for (Although we do plan to migrate to a self hosted GitHub Actions runner), see https://github.com/testcontainers/testcontainers-java/blob/master/azure-pipelines.yml |
|
From my experiments it doesn't work with which looks like the same error like the one of @jonashackt in the linked commit above |
…since Windows Server 2019 isn't supported right now by Testcontainers testcontainers/testcontainers-java#2960).
…since Windows Server 2019 isn't supported right now by Testcontainers testcontainers/testcontainers-java#2960).
|
@LorenzoBettini not a real fix, but we went with the workaround to not run testcontainers tests on Windows right now - but have all the other tests and the build there. Therefore we used |
|
@jonashackt I basically did the same ;) |
|
i've actually been able to start a BrowserWebDriver container on my windows 2019 vm but when I try getWebDriver() I hit this error - org.rnorth.ducttape.TimeoutException: Timeout waiting for result with exception Has there been any progress on this? |
|
@amyreit Can you please specify which steps and workaround you did to get Testcontainers working to this point on Windows Server 2019 with LCOW enabled? Also, can you please verify if this example works with your setup? |
|
my bad, it was late and I was desperately googling "unable to get webdriver from testContainer on windows" - missed that this issue was using LCOW. I'm using a plain windows docker container. But I then also later read that any use of testContainers on 2019 is unsupported, so I assume I am just out of luck? |
|
How do you define Windows Docker Container in this case? Windows container should not directly work with Testcontainers and more specifically, I don't think the Selenium images in Did you try running the example I linked to above in your setup? This would help us understand the actual problem better. |
|
Is there any shortlist of issues/tasks to be solved to make Testcontainers work on WCOW? I'd like to help and enable native WCOW support. Creating multi-arch/multi-platform images for Ryuk should only be a matter of time (been there for my own projects), but I suspect there might be harder issues to be solved? edit: I'm going to create a dedicated issue. |
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:
Docker Info as below:
The text was updated successfully, but these errors were encountered: