windows-images: Windows-containers launched by selenoid do not respond in 30s

So i have built the windows-images according to the guide (which was very helpful) and played around with them for a big and have encountered one issue. When i try to launch these images with Selenoid, the container fails to start with the following message:

selenoid_1     | 2019/11/13 11:09:26 [1] [SERVICE_STARTUP_FAILED] [wait: does not respond in 30s]

However when i launch the containers myself i can connect to them via vnc just fine and also tests against the Webdriver running inside work. So my only issue is the containers not seeming to work together with Selenoid.

I am using docker-compose to launch selenoid together with selenoid-ui, the docker-compose file:

version: '3'
    image: aerokube/selenoid:latest-release
      - "/home/wdadm/selenoid/config/:/etc/selenoid"
      - "/var/run/docker.sock:/var/run/docker.sock"
      - "4444:4444"
      - internal
    command: ["-container-network","selenoid_internal"]
    image: "aerokube/selenoid-ui"
      - "8080:8080"
    command: ["--selenoid-uri","http://selenoid:4444"]
      - internal
    driver: bridge

I am doing all this on Ubuntu 18.04 running in a Hyper-V on Windows 10

About this issue

  • Original URL
  • State: open
  • Created 5 years ago
  • Comments: 46 (13 by maintainers)

Most upvoted comments

@toni-moreno I have had this issue aswell when i was using the 3.150 IEDriverServer When i switched back to the 3.141.59 it seemed to not occur again

@NavySeal5 @emilorol I switched to the 32b version and the senkeys issue has been resolved for me