Images can be quite small. Debian slim image is 25.9 MB compressed. Alpine image is 2.7 MB compressed. Meanwhile, Selenium’s standalone Chromium image is 348.1 MB compressed.

> 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:

    apt-get update -qq && \
    apt-get install -qq -y --no-install-recommends \
        wget curl chromium git ffmpeg youtube-dl \
        fontconfig fonts-ipafont-gothic fonts-wqy-zenhei fonts-thai-tlwg fonts-kacst fonts-symbola fonts-noto fonts-freefont-ttf && \  
    rm -rf /var/lib/apt/lists/*

https://hub.docker.com/layers/nikisweeting/archivebox/latest...

Any 10MB here or there will help, whether it's from Chrome core or something else. If you have any suggestions I'm all ears!

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?

The fonts are for PDF and screenshot rendering.

Have you considered doing the install at usage time? If you're trying to save on bandwidth of downloaded images....

Doesn't help, they're used almost immediately.

Maybe give this a try: https://github.com/docker-slim/docker-slim