You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I see the old Docker Hub registries contained an arm64 build as well as an intel build, but the new registry doesn't seem to (I seem to only get a single image without any tagged architecture, and it definitely doesn't run on an ARM host).
I think it would be nice to also provide arm builds; it is becoming increasingly popular on both laptops and servers.
I have a DocSpell instance running using these images on an ARM server at https://docspell.westergaard.cloud/ – I just changed the images and the nodeSelector and things seem to just work.
No changes were necessary to make the build manually, just running the script on an ARM machine. In principle, it's also possible to "cross-compile" using dockerx, but that's terribly slow.
I can see about making the change to the Github CI files to run on an ARM machine, but I'm not terribly familiar with GitHub's CI system.
it might be somewhat simple to do this using a matrix build, running the current job once per arch, producing the full image as a job output and then having a new job that collects the outputs and builds the multi-arch manifest
Activity
pschichtel commentedon Apr 27, 2026
@eikek Does docspell itself carry any platform dependent code? Or does it ship multiple architectures anyway?
klafbang commentedon May 3, 2026
It seems there's no (obvious) platform-dependent code in the distributed .zip.
I tried blindly building ARM images manually using the script in this repo, and from the testing I've done so far, it seems to work.
My images are presently in https://gitlab.westergaard.eu/klafbang/docspell/container_registry
I have a DocSpell instance running using these images on an ARM server at https://docspell.westergaard.cloud/ – I just changed the images and the
nodeSelectorand things seem to just work.pschichtel commentedon May 3, 2026
are you willing to contribute the necessary changes here?
klafbang commentedon May 3, 2026
No changes were necessary to make the build manually, just running the script on an ARM machine. In principle, it's also possible to "cross-compile" using dockerx, but that's terribly slow.
I can see about making the change to the Github CI files to run on an ARM machine, but I'm not terribly familiar with GitHub's CI system.
pschichtel commentedon May 3, 2026
it might be somewhat simple to do this using a matrix build, running the current job once per arch, producing the full image as a job output and then having a new job that collects the outputs and builds the multi-arch manifest