Testing Joplin Server on ARM64?

Lounge
1

The latest version of Joplin Server 3.3.13 is available as both AMD64 and ARM64 images. As far as I know the ARM64 version should work fine but I'm not able to directly test it. I'm wondering if anyone might have an ARM64 device where they could test this release? It is available at the usual place: https://hub.docker.com/r/joplin/server/tags

3

Hi,

Unfortunately, I can't test the ARM64 image because I no longer use this architecture.

For the record, I was using the 3.3.4-beta image on AMD64, which was updated yesterday to 3.3.9-beta by Renovate. Since 3.3.9-beta doesn't have an AMD64 image, it failed to start. I manually set the image tag to 3.3.13, and it works again.

I'm just sharing this in case someone else encounters the same issue.

Anyway, thanks for the official ARM64 image! :wink:

1 Like
4

So far, it seems to work!

I'm running the Docker container on Debian 12 (ARM64) with the following command:

bash$ sudo docker run --env-file .env -p 22300:22300 joplin/server:arm64-3.3.13

I was able to:

  • Open the web interface.
  • Change the default admin password and create a user.

I haven't tried syncing yet. Edit: Sync also works, with a copy of joplin-desktop (snap, ARM64) running on the same computer.

1 Like
5

Hi, Laurent - I have tested 3.3.13 on an ARM64 device - it does work. However, there is one bug. When you pull a new image and update the docker stack, this results in erasing all users and data. After taking this action, a new instance is created - but you have sign in (again) with the default username and PW and are effectively starting over from scratch unless you saved your data via a jex file. I tested this by first building an instance with joplin/server:3.3.13, and then pulled a new image with joplin/server:arm64-latest. Hopefully this gives some direction on how to fix this issue. Best.

6

But how do you update the image? Normally it's not possible for the data to disappear as the images doesn't contain any.

7

Laurent - apologizes. There was something wrong in my docker-compose file that was causing the issue. Everything seems to be working well now. I'll follow up if I experience anything else.

1 Like
8

Great to hear, and thank you for testing!