Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Joplin Server does not support ARM, causes exec format error #4937

Closed
water-sucks opened this issue May 8, 2021 · 18 comments
Closed

Joplin Server does not support ARM, causes exec format error #4937

water-sucks opened this issue May 8, 2021 · 18 comments
Labels
stale An issue that hasn't been active for a while...

Comments

@water-sucks
Copy link

It seems that the Joplin Server Docker image does not have support for ARM-based CPUs. I pulled the image on a Raspberry Pi 3B+ and the Docker logs report that there is an exec format error and keeps on restarting the container.

Environment

Joplin version: server (latest)
Platform: Linux aarch64 Docker (Raspberry Pi 3B+)
OS specifics: Void Linux 64-bit ARM (aarch64 Raspberry Pi 3 rootfs), zsh shell

Steps to reproduce

  1. Write docker-compose file exactly as-is in the sample
  2. Run command sudo docker-compose up -d
  3. Check logs using sudo docker logs <container id> &> joplin-logs.log

Describe what you expected to happen

I expected the Joplin server to be up and running without any issues.

Logfile

(using Docker logs, as there are no specific procedures listed in link for how to get logs for server)

docker-logs.log

@water-sucks water-sucks added the bug It's a bug label May 8, 2021
@laurent22 laurent22 removed the bug It's a bug label May 8, 2021
@dpoulton-github
Copy link

Your report appears to answer your own question,

It seems that the Joplin Server Docker image does not have support for ARM-based CPUs.

However, florider89 (florider on the forum) has created an ARM64 compatible docker image.

https://hub.docker.com/r/florider89/joplin-server

I have tried it and it works fine on RasPiOS x64.

I am just another user so I do not know if Laurent ever intends to release a server version that supports ARM.

@water-sucks
Copy link
Author

Ah, I did not see this. Great to know that there is such an image available. My apologies.

@TheGreatestJannet
Copy link

It would be nice to have an official arm64 image though!

@dpoulton-github
Copy link

It would be nice to have an official arm64 image though!

Yes it would!

@stale
Copy link

stale bot commented Jun 20, 2021

Hey there, it looks like there has been no activity on this issue recently. Has the issue been fixed, or does it still require the community's attention? This issue may be closed if no further activity occurs. You may comment on the issue and I will leave it open. Thank you for your contributions.

@stale stale bot added the stale An issue that hasn't been active for a while... label Jun 20, 2021
@TheGreatestJannet
Copy link

This issue isn’t fixed.

@stale stale bot removed the stale An issue that hasn't been active for a while... label Jun 20, 2021
@dpoulton-github
Copy link

This issue isn’t fixed.

I guess that's because it's not a bug. Joplin server is not built to run on ARM, so ARM support is a feature request. This feature request is being brought up on the forum and, it seems, @laurent22 is happy for someone to work on it.

https://discourse.joplinapp.org/t/major-breaking-change-in-coming-joplin-server-2-0/17254/93

@TheGreatestJannet
Copy link

This is true. Is there a feature request tag to add or are they meant to be on the forum?

@dpoulton-github
Copy link

Is there a feature request tag to add or are they meant to be on the forum?

Feature requests currently get discussed on the forum with GitHub used for bug issues. They are mainly in the "Features" category, however they can appear in others such as "Beta Testing". I believe that this is because more users engage on the forum than here, so there is a wider set of opinions.

IIRC, if you actually try to raise a feature request on GitHub you get referred to the forum.

@mu88
Copy link
Sponsor

mu88 commented Jul 11, 2021

However, florider89 (florider on the forum) has created an ARM64 compatible docker image.

https://hub.docker.com/r/florider89/joplin-server

I have tried it and it works fine on RasPiOS x64.

Which Raspberry Pi did you use? I was not able to pull the Docker image on my Raspberry Pi 4 (see here).

@dpoulton-github
Copy link

I used a Pi4 but the important bit is that you use the RasPiOS Beta 64-Bit image. The default / standard RasPiOS is only 32-bit.

https://downloads.raspberrypi.org/raspios_lite_arm64/images/

@abhilesh
Copy link

I have a 64 bit image, the output for my uname -a is
Linux raspberrypi 5.10.44-v8+ #1429 SMP PREEMPT Fri Jun 25 10:03:37 BST 2021 aarch64 GNU/Linux
and yet I run into the no matching manifest for linux/arm/v7 in the manifest list entries while pulling florider89/joplin-server:latest.

I am confused as to why docker doesn't pull the right image

@dpoulton-github
Copy link

@abhilesh

I can't replicate this. My Pi4 with RaspiOS x64 Lite pulls the image just fine.

Maybe you should join @mu88 on the GitHub issue they raised with the ARM image's dev?

flosoft/docker-joplin-server#7

@abhilesh
Copy link

I was able to resolve this by making two modifications in my docker-compose file.

The first one was to use the master tag for the image, hence pulling florider89/joplin-server:master.
The second was to explicitly declare the platform by adding platform: linux/arm64 under app:

Hope this helps!

@dpoulton-github
Copy link

Did you see florider's comments about the tags / master tag?

master[-alpine]: Images built testing CI / Image changes. Should not be used on systems you want to have a working instance of Joplin Server on. Currently V2 Beta - see notice at the top!

@abhilesh
Copy link

I missed that comment, thanks for bringing it to my attention. I am just starting out with joplin, so I don't mind being on the experimental build right now.

However, I can confirm all tags work by including the platform: linux/arm64 in docker-compose

@stale
Copy link

stale bot commented Aug 18, 2021

Hey there, it looks like there has been no activity on this issue recently. Has the issue been fixed, or does it still require the community's attention? This issue may be closed if no further activity occurs. You may comment on the issue and I will leave it open. Thank you for your contributions.

@stale stale bot added the stale An issue that hasn't been active for a while... label Aug 18, 2021
@stale
Copy link

stale bot commented Sep 3, 2021

Closing this issue after a prolonged period of inactivity. If this issue is still present in the latest release, please feel free to create a new issue with up-to-date information.

@stale stale bot closed this as completed Sep 3, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
stale An issue that hasn't been active for a while...
Projects
None yet
Development

No branches or pull requests

6 participants