Failed to start tunnel - null or selenium tunnel about digdug HOT 3 CLOSED

Possible causes:

1. For null tunnel, did you manually start Selenium or chromedriver on the Jenkins server? null tunnel only works with an already-running webdriver server.
2. For selenium tunnel, does the Jenkins server have Java? Selenium requires Java.

When null tunnel is initialized it simply attempts to connect to an already running webdriver server or Selenium.

Selenium tunnel handles more of the webdriver startup process. When the Selenium tunnel is initialized it downloads Selenium and any necessary webdrivers (this is why you see the 'downloading' message), and then starts Selenium. Note that Java is required to run Selenium.

from digdug.

About the null tunnel, I had a bug in my config loader, so I accidentally loaded config with a selenium tunnel. So null tunnel works fine.

For the selenium tunnel I manage to extract the error message, which would be nice to have without meddling with the Tunnel.js.

The problem is that my docker container is missing Java. I tried installing it using wget, but it still didn't work.

Any idea how to install java for my selenium tunnel in my dockerfile?

from digdug.

I agree, the error message could definitely be better; there's actually an open issue for that.

Regarding how to install java in your docker container, it depends on your setup, but there are numerous examples online.

from digdug.