Switch to Chrome to avoid 429s

[mod242]

Switch to chrome-stable and make chromedriver dynamic to installed chrome-version.
This solves shadow-bans for me on docker and should be future-proof, becuase the correct chrome-driver is evaluated by installed google-chrome.

[J0ekr]

I'm not able to build the docker image for this repo with the following error.

E: Unable to locate package google-chrome-stable

Removing intermediate container ef8096c6ff01

ERROR: Service 'impf-botpy' failed to build : The command '/bin/sh -c 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.list &&     apt-get update -y &&     apt-get install -y google-chrome-stable &&     CHROMEVER=$(google-chrome --product-version | grep -o "[^\.]*\.[^\.]*\.[^\.]*") &&     DRIVERVER=$(curl -s "https://chromedriver.storage.googleapis.com/LATEST_RELEASE_$CHROMEVER") &&     wget -q --continue -P /chromedriver "http://chromedriver.storage.googleapis.com/$DRIVERVER/chromedriver_linux64.zip" &&     unzip /chromedriver/chromedriver* -d /usr/local/bin &&     rm -r -f /chromedriver/' returned a non-zero code: 100

As there are multiple things happening in this command I cant really check where the error lies.

[mod242]

What platform do you try to build on? Seems like the build process can't find the google chrome package (which works on my x86_64)

[J0ekr]

On a raspberry pi, so there might be no arm version for google-chrome-stable - didn't think about that.

[mod242]

Just checked, that's the reason :-( Have no idea how to easly come around this

[alfonsrv]

Can confirm this fixes it. Merging to main.

Thanks for contributing @mod242