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

Selfhosted

40439 readers
789 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
 

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
[–] HorseFD 1 points 1 year ago* (last edited 1 year ago) (1 children)

I've just given the script a go and it seems to have failed

=> => transferring context: 23.07MB                                                                                                                                                                                                                                                                                   0.2s
 => [lemmy lemmy 2/6] RUN apt-get update  && apt-get -y install --no-install-recommends postgresql-client libc6 libssl1.1 ca-certificates  && rm -rf /var/lib/apt/lists/*                                                                                                                                             18.7s
 => [lemmy builder 2/7] RUN apt-get update  && apt-get -y install --no-install-recommends libssl-dev pkg-config libpq-dev git  && rm -rf /var/lib/apt/lists/*                                                                                                                                                         14.7s
 => [lemmy lemmy 3/6] RUN addgroup --gid 1000 lemmy                                                                                                                                                                                                                                                                    0.5s
 => [lemmy lemmy 4/6] RUN useradd --no-create-home --shell /bin/sh --uid 1000 --gid 1000 lemmy                                                                                                                                                                                                                         0.4s
 => [lemmy builder 3/7] WORKDIR /app                                                                                                                                                                                                                                                                                   0.0s
 => [lemmy builder 4/7] COPY ./ ./                                                                                                                                                                                                                                                                                     0.2s
 => [lemmy builder 5/7] RUN echo "pub const VERSION: &str = "$(git describe --tag)";" > "crates/utils/src/version.rs"                                                                                                                                                                                                  0.2s 
 => ERROR [lemmy builder 6/7] RUN cargo build --release                                                                                                                                                                                                                                                              399.8s 

Altough the building timer is still running

[+] Building 761.3s (15/18)

Is there somewhere I can access logs to see what happened?

Edit: Managed to screenshot the error prior to it disappearing

[–] [email protected] 1 points 1 year ago* (last edited 1 year ago) (1 children)

Well, that's a new one. Never seen a build fail before.

I see some issues on Lemmy's tracker about builds failing due to network issues. Something about not being able to clone files it needs for the build.

Can you try the build again, and if this happens consistently, file an issue on my tracker? I'll try to reproduce the issue and fix it if possible.

[–] HorseFD 1 points 1 year ago

I tried again on a new server, and I'm still getting the same error. It may be related to this:

https://github.com/LemmyNet/lemmy/issues/3235

I see the same references to email_verified_body and email_verified_subject