Image sizes

[shwoop]

I was surprised at the size of the amd64 image and the striking differnece compared with arm64.

I started to do some investigations.

$ uname -a
Linux manjaro 6.18.12-1-MANJARO #1 SMP PREEMPT_DYNAMIC Mon, 16 Feb 2026 21:35:51 +0000 x86_64 GNU/Linux
$ docker image ls | grep paperless
WARNING: This output is designed for human readability. For machine-readable output, please use --format.
clusterzx/paperless-ai:latest                        c677e2a0b969       8.59GB             0B        
ghcr.io/paperless-ngx/paperless-ngx:latest           67aa270f9547       1.42GB             0B   U    
paperless-ai-dev:0c3f5a7                             99506752d2b3       1.92GB             0B   U    
paperless-ai-dev:eaa64e0                             09fca76f1fb8       8.36GB             0B        
paperless-ai-dev:main                                42fe2fbd6abc       8.77GB             0B       

eaa64e0 uses a dev steage when building so knocks a few hundred MB off the size. (Draft PR #889)

I'm currently running 0c3f5a7 (not tested RAG) which installs a CPU only version of torch:

$ head -2 requirements.txt 
--index-url https://pypi.org/simple
--extra-index-url https://download.pytorch.org/whl/cpu

I don't see any mention in the documentation about enabling hardware acceleration so would it be possible to drop this? Or maybe offer another image tag?

I have seen a previous discussion about image size but it did not contain much information: #597

Also, I noticed that the image contains a zip file. Is this needed? I cannot see any links to it on the UI and suspect that it's the chrome extension mentioned in the FAQ (although renamed) https://github.com/clusterzx/paperless-ai/wiki/5.-FAQ

$ docker run -it clusterzx/paperless-ai:latest ls | grep .zip
docker-compose.yml   paperless-ai-chrome.zip  swagger.js