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.
I built my own arm64 v0.17.4 docker image. It’s available on docker hub:
mpatton/lemmy:0.17.4-linux-armmpatton/lemmy-ui:0.17.4-linux-armWhat are you using as your reverse proxy?
The docker docs are out of date. You need to expose the lemmy service to an external network. I created a third network called
lemmybridgeand added it to thelemmyservice.I had to work out all of the issues myself to get it working on my RaspberryPi 4. For this error, did you add a network to your “lemmy” container that would allow it access to the internet?
https://github.com/LemmyNet/lemmy/issues/3167#issuecomment-1595846910
I’m still using 0.17.3, btw. I haven’t checked if 0.17.4 for arm64 is out yet.
Edit: Just checked and it looks like they’re just skipping past 0.17.4 and moving on to 0.18.0 on their docker hub. https://hub.docker.com/r/dessalines/lemmy/tags
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.
ARM64 docker images (unfortunately 0.17.4 images don’t exist yet).
I would use the “Lemmy from Scratch”, and go with using github checkout for lemmy_server code.
I’m running my instance on ARM64 on Oracle Cloud, they are giving out free ARM systems with 24GB of RAM and 200GB storage.
That does sound incredibly good for free.
Did you have any issues with pict-rs? Is it indeed included within the lemmy-server binary?
That does sound incredibly good for free.
It’s a little too good to be true, they have been known to shut down people without notice… I wouldn’t rely on it. And the screens to use it are kind of tricky, but there are lots of instruction videos, blogs and Reddit postings about it.
Did you have any issues with pict-rs? Is it indeed included within the lemmy-server binary?
I skipped that for now. I don’t think ARM64 matters, Linux is Linux. I skipped it as I didn’t want to take on policing images people upload, but as Lemmy improves I might change my mind.
I see no reason ARM64 should matter for Lemmy vs. x86, this is run of the mill stuff like PostgreSQL, Rust,m NodeJS.
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?
I might try building from scratch again and running pict-rs in a docker container.
