I’m interested in running Lemmy on an ARM64 host, mostly just for fun and because it’s possible.

I’ve tried a couple of things without getting it right yet:

Building from scratch on Ubuntu 20.04 This went quite well but I was unable to get pict-rs working, so there was no image hosting. I followed this guide: https://join-lemmy.org/docs/administration/from_scratch.html I had to build imagemagick to get the ARM64 binary, however pict-rs did not run. Is it correct that it’s included with the lemmy-server binary or am I understanding how it works wrong?

Using Docker images I was able to get Lemmy up and running using 0.17.3 ARM64 docker images (unfortunately 0.17.4 images don’t exist yet). I set up an nginx reverse proxy on the host and was able to access the instance OK, however there was no connectivity between my instance and external sites. Looking in the logs I saw timeout errors:

lemmy_1     | LemmyError { message: None, inner: Request error: error sending request for url (https://kbin.social/u/Emptiness): operation timed out
lemmy_1     | 
lemmy_1     | Caused by:
lemmy_1     |     0: error sending request for url (https://kbin.social/u/Emptiness): operation timed out

So I was wondering if anybody had a guide out there to hosting Lemmy (preferably 0.17.4) on an ARM64 host, either by building it from scratch or by using Docker images. Or any other method really.

  • studcavity@discuss.tchncs.deEnglish
    1·
    2 years ago

    That second error is not a matter of your ARM64 architecture, but a networking thing. If you launch a bash shell in your container, does any network activity work? That will tell you if it’s the container, or just Lemmy.

  • dudeami0@lemmy.dudeami.winEnglish
    1·
    2 years ago

    I have the same errors regarding kbin.social with my instances running on x86_64, and have yet been successful in federating with them on 0.17.4. I am subscribed to 4 of their “magazines”, but cannot get content to start coming in, and have similar errors:

    LemmyError { message: None, inner: Request error: error sending request for url (https://kbin.social/u/Larvitar): operation timed out

    lemmy.ml instances seem to get stuck on pending subscription as well. Other instances I have subscribed to have no issue. Sorry this doesn’t answer your arm64 question, but just wanted to share those errors aren’t limited to arm64.

  • Jattatak@lemmy.bulwarkob.comEnglish
    1·
    2 years ago

    The default docker-compose.yml from the guide has the docker lemmy network set as internal. You need to make it not an Internal network.

    Source: Did the same thing with the same problem, on Oracle ARM64 VPS.

  • exu@feditown.comEnglish
    0·
    2 years ago

    The easiest would probably be waiting for official ARM containers for 0.17.4. You could also build the containers yourself, the dockerfile should be somewhere in the Lemmy repositories.

    Also, nothing’s stopping you from building Lemmy from scratch and having Postgres and pictrs in container. Just make sure to forward the necessary ports.

    No idea what the error is unfortunately. Are you sure you set all ENV and config variables correctly?

  • falcon15500@lemmy.nine-hells.netEnglish
    0·
    2 years ago

    I built my own arm64 v0.17.4 docker image. It’s available on docker hub:

    mpatton/lemmy:0.17.4-linux-arm

    mpatton/lemmy-ui:0.17.4-linux-arm

    What are you using as your reverse proxy?