this post was submitted on 22 Jun 2023
42 points (100.0% liked)

Selfhosted

40400 readers
791 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 2 years ago
MODERATORS
ruud
Loki
CannaVet
devve
HybridSarcasm
[email protected]
42
Is there a guide to hosting Lemmy on an ARM64 machine? (self.selfhosted)
submitted 1 year ago* (last edited 1 year ago) by HorseFD to c/selfhosted
46 comments fedilink hide all child comments
 

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.

you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 2 points 1 year ago (2 children)

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.

[–] [email protected] 2 points 1 year ago (1 children)
[–] [email protected] 1 points 1 year ago

I'm not sure this applies to me since I'm hosting on kubernetes, but thanks for sharing that link. I can communicate with any instance other than kbin, and lemmy.ml just seems spotty/inconsistent (I assume it's overloaded slightly still).

[–] HorseFD 1 points 1 year ago

In this case, it just so happened to be kbin.social in the example I posted. In my case it's every outbound connection timing out.