ARM support for focalboard

[ghost]

Cannot use focalboard_enabled on ARM using this playbook.

Always fails at this step:

TASK [galaxy/com.devture.ansible.role.systemd_service_manager : Fail if service isn't detected to be running] *********************
failed: [mash.redacted.com] (item=mash-focalboard.service) => {"ansible_loop_var": "item", "changed": false, "item": "mash-focalboard.service", "msg": "mash-focalboard.service was not detected to be running. It's possible that there's a configuration problem or another service on your server interferes with it (uses the same ports, etc.). Try running `systemctl status mash-focalboard.service` and `journalctl -fu mash-focalboard.service` on the server to investigate. If you're on a slow or overloaded server, it may be that services take a longer time to start and that this error is a false-positive. You can consider raising the value of the `devture_systemd_service_manager_up_verification_delay_seconds` variable. See `/home/daries/mash-playbook/roles/galaxy/com.devture.ansible.role.systemd_service_manager/defaults/main.yml` for more details about that."}

journalctl

Mar 21 20:14:55 daries systemd[1]: mash-focalboard.service: Failed with result 'exit-code'.
Mar 21 20:15:26 daries systemd[1]: mash-focalboard.service: Scheduled restart job, restart counter is at 20.
Mar 21 20:15:26 daries systemd[1]: Stopped Focalboard (mash-focalboard).
Mar 21 20:15:26 daries systemd[1]: Starting Focalboard (mash-focalboard)...
Mar 21 20:15:26 daries mash-focalboard[4118180]: WARNING: The requested image's platform (linux/amd64) does not match the detected host platform (linux/arm64/v8) and no specific platform was requested
Mar 21 20:15:26 daries mash-focalboard[4118180]: c69ada62b00a9789f656f00fc50119fee77f0816f1b24a85845fada520e45d1a
Mar 21 20:15:26 daries systemd[1]: Started Focalboard (mash-focalboard).
Mar 21 20:15:26 daries mash-focalboard[4118240]: exec /opt/focalboard/bin/focalboard-server: exec format error
Mar 21 20:15:27 daries systemd[1]: mash-focalboard.service: Main process exited, code=exited, status=1/FAILURE
Mar 21 20:15:27 daries systemd[1]: mash-focalboard.service: Failed with result 'exit-code'.

[spantaleev]

The mattermost/focalboard image published to Docker Hub only supports the amd64 architecture.

Our focalboard Ansible role does not yet support self-building of container images when the required architecture does not match.

Looking at the Focalboard issues, there may be problems with building the image right now.

The image provided on Docker Hub is also very outdated, as I've posted about here: mattermost-community/focalboard#4651

You can try building the image yourself and let us know how it goes. You can also try adding self-building support to our Focalboard Ansible role, inspired by one of the other roles that support self-building. The matrix-bot-chatgpt role (part of matrix-docker-ansible-deploy) is a good template.

[ptman]

mattermost-community/focalboard#5038 - focalboard seems to be unmaintained

[5FeetUnder]

The mattermost/focalboard image published to Docker Hub only supports the amd64 architecture.

this is actually what motivated me to create a simple github action to build an arm64 image for focalboard: 5FeetUnder/focalboard-arm64-docker

Currently I've only built for v7.11.3 since this is the latest version of the latest release for the standalone server, but I just started the action to build v7.10.4 (which seems to be the configured version in MASH if I'm not mistaken)

Maybe this could be incorporated into the playbook somehow or the workflows inspire some other solution or something.