Skip to content

ARM builds #36

Open
Open

Description

@klafbang

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.

It seems it should be relatively easy to build arm images on Github, https://github.blog/news-insights/product-news/arm64-on-github-actions-powering-faster-more-efficient-build-systems/, but of course it also requires arm native docspell releases since the image currently downloads those.

Activity

  1. pschichtel commented on Apr 27, 2026

    @pschichtel
    Collaborator

    @eikek Does docspell itself carry any platform dependent code? Or does it ship multiple architectures anyway?

  2. klafbang commented on May 3, 2026

    @klafbang
    Author

    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 nodeSelector and things seem to just work.

  3. pschichtel commented on May 3, 2026

    @pschichtel
    Collaborator

    are you willing to contribute the necessary changes here?

  4. klafbang commented on May 3, 2026

    @klafbang
    Author

    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.

  5. pschichtel commented on May 3, 2026

    @pschichtel
    Collaborator

    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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions