> Meanwhile, Selenium’s standalone Chromium image is 348.1 MB compressed.
Selenium implies you have quite a bit of a developer stack, runtimes and SDKs installed too. It would be unfair to attribute all that usage to Chrome alone.
Not aware of the docker image in question, but a docker image starts empty (0 bytes). A full operating system (Ubuntu 20.04) base is is 75MB.
You can probably slim that down a bit if you needed, but installing your software on top might only take a few MB. So cutting chrome down from 60MB could well be a good goal.
Unfortunately our image is ~450MB right now because we have install both Python and JS, Chrome, fonts, vido codecs, and a bunch of other software for all the extractors.
Most of it is from this killer 266MB line, but unfortunately we need all these things:
Yeah the fonts take alot. Why do you need to slim the images down? Do you really need the fonts present to archive the content, I thought you were saving the HTML, wouldn't these fonts just be needed to render?
Is there a docker POC anywhere I can check out?
https://github.com/cxreet/chromium-debloating seems empty at the moment.