Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Docker: Chrome 107 doesn't have debian package
See original GitHub issue🐛 Bug
Chrome LATEST_RELEASE is currently 107.0.5304.62, but the url https://dl.google.com/linux/chrome/deb/pool/main/g/google-chrome-stable/google-chrome-stable_107.0.5304.62-1_amd64.deb is a 404.
To Reproduce
Run docker build . in root directory.
Workaround
Pass --build-arg CHROME_VERSION=106.
Issue Analytics
- State:
- Created a year ago
- Comments:6 (6 by maintainers)
Top Results From Across the Web
How do I install a specific version of Chrome in a Dockerfile?
Have a Dockerfile that installs from a python image and then I need it to install a specific (not latest) version of Google...
Read more >How to setup chrome browser and chromedriver with Docker?
Now i have to build my app on Amazon Ubuntu 20.04 server using docker-compose, i tried lots of different ways but stil can't...
Read more >Install older versions of google-chrome-stable, on ubuntu 14.10
I know this question is a bit old, but in case you came here willing to do this from the terminal, you can...
Read more >Install Docker Engine on Debian
To install Docker Engine, you need the 64-bit version of one of these Debian or ... The script doesn't allow you to customize...
Read more >Installing Google Chrome On CentOS, Amazon Linux, or RHEL
Google does maintain a repository with a Chrome RPM package, but it only works with RHEL/CentOS 7.X versions. Amazon Linux is currently only...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
It seems like the chrome versionhistory API is broken (returning strange results):
It only shows linux versions with <= 88
while it shows windows versions correctly.
I think the chrome team will soon fix this, so let’s wait for a few days and if the API is still broken, I’ll try to find an alternative way to retrieve chrome versions…
It looks like the linux API endpoint now shows correct result.