CHROME_DRIVER_VERSION usage

[alievrouw]

I trying to bring up a chrome-node with this syntax:

-e CHROME_DRIVER_VERSION=2.12

The resulting chromedriver version is still 2.21 (the default from the dockerfile). Am I calling this environmental variable incorrectly?

[jmieleiii]

Chrome node doesn't appear to have an ENV variable for setting the version

#===============
# Google Chrome
#===============
RUN wget -q -O - https://dl-ssl.google.com/linux/linux_signing_key.pub | apt-key add - \
  && echo "deb http://dl.google.com/linux/chrome/deb/ stable main" >> /etc/apt/sources.list.d/google-chrome.list \
  && apt-get update -qqy \
  && apt-get -qqy install \
    google-chrome-stable \
  && rm /etc/apt/sources.list.d/google-chrome.list \
  && rm -rf /var/lib/apt/lists/*

[alievrouw]

I'm confused, it's here no:
https://github.com/SeleniumHQ/docker-selenium/blob/365a9831aa793f7eeec00d22b0decf3328a961dc/NodeChrome/Dockerfile

#==================

Chrome webdriver

#==================
ENV CHROME_DRIVER_VERSION 2.21
RUN wget --no-verbose -O /tmp/chromedriver_linux64.zip https://chromedriver.storage.googleapis.com/$CHROME_DRIVER_VERSION/chromedriver_linux64.zip
&& rm -rf /opt/selenium/chromedriver
&& unzip /tmp/chromedriver_linux64.zip -d /opt/selenium
&& rm /tmp/chromedriver_linux64.zip
&& mv /opt/selenium/chromedriver /opt/selenium/chromedriver-$CHROME_DRIVER_VERSION
&& chmod 755 /opt/selenium/chromedriver-$CHROME_DRIVER_VERSION
&& ln -fs /opt/selenium/chromedriver-$CHROME_DRIVER_VERSION /usr/bin/chromedriver

[jmieleiii]

Sorry, I confused your question with being able to set the Chrome browser version vs ChromeDriver version.

[testphreak]

Yeah, I tried the same thing and didn't work for me either. Trying to have node chrome use v2.22.

[JesseChezenko-AI]

@adamlievrouw When the image is built the Dockerfile code is executed. ( ie. chrome driver is installed )

Setting an environment variable when starting a container, docker run -e CHROME_DRIVER_VERSION=2.12 node-chrome, will have no effect on the chrome driver version installed on the container.

Note there is a pull request to update chrome driver here. #234

[F2X]

Maybe it should be a ARG variable and not an ENV one in the Dockerfile?
Moreover I think we needs to find a way to offer an option to change versions on runtime, I have some issues with the couple Firefox / webdriver, which is often broken, and allowing end-user to set these values can be a plus.

[ddavison]

it definitely should be an arg, and specified by docker build -t my-firefox-image --build-arg CHROME_DRIVER_VERSION=2.23 for example. I've already updated it and released it in 2.53.1-americium.

@F2X has a pull request that was just merged and will fix the same functionality with Firefox. This functionality will be released as 2.53.1-beryllium

@adamlievrouw,

to fix this, you will need to build your own docker image. (these images were designed that way, anyway.) you can build your own image with the chromedriver version you want by the following:

$ BUILD_ARGS="--build-arg CHROME_DRIVER_VERSION=<version_desired>" make build

or by manually invoking docker build