Closed dryu99 closed 2 years ago
Nevermind, figured it out! Although I couldn't use apt-get to install older Chromium versions, I was able to copy over downloaded packages from https://chromium.cypress.io/ into specific paths to get it working. I also had to create a symlink so seleniarm would be able to execute the binary properly.
COPY ./chrome-linux /usr/lib/chromium/
RUN chmod -R +x /usr/lib/chromium/
# create symlink for binary
RUN ln -s /usr/lib/chromium/chrome /usr/bin/chromium
# other instructions...
COPY ./chromedriver_linux64/chromedriver /usr/bin/chromedriver
RUN chmod +x /usr/bin/chromedriver
What happened?
I'm trying to use older versions of Chromium in my Selenium Grid setup, however when I try setting an older version in the
NodeChromium
Dockerfile I get the following error:Where I've been using https://chromium.cypress.io/ to pick stable versions. If installing older versions doesn't work through through
apt-get
, would it be possible to install an older version manually in the image if I have the binary? When I rundpkg -L chromium
to see what files are installed I get this:And when I download a chromium package from https://commondatastorage.googleapis.com/chromium-browser-snapshots/index.html?prefix=Linux/, the following files are present:
There doesn't seem to be a 1-1 mapping of files from the
apt-get
and manual installation, I'm assuming I don't need every file to be present except for some important ones such as thechromium
binary. Would it be enough to just renamechrome
->chromium
? Or maybe there's more I'm missing and it's not that straightforward. If anyone has any thoughts on this please let me know, regardless thanks for all your work on this fork!Command used to start Selenium Grid with Docker
Relevant log output
Operating System
Ubuntu
Docker Selenium version (tag)
seleniarm-v4.4.0-20220814