[feat] arm64 OTP and Docker builds #424
Labels
No labels
approved, awaiting change
bug
configuration
documentation
duplicate
enhancement
extremely low priority
feature request
Fix it yourself
help wanted
invalid
mastodon_api
needs docs
needs tests
not a bug
planned
pleroma_api
privacy
question
static_fe
triage
wontfix
No milestone
No project
No assignees
3 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: AkkomaGang/akkoma#424
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
The idea
Arm64 OTP and Docker images
The reasoning
I would like to run Akkoma on a Pi4, but building it manually takes a lot of time.
Have you searched for this feature request?
sadly i can't really afford any more infrastructure to build OTPs on
How are the OTPs being build? Oracle provides free tier arm64 boxes with 4 cores, 24gb memory and 50gb space. I used one to try building an arm64 image, it was fast. Maybe I could put a runner on it?
oracle is 100% out of capacity in my region, this will have to wait on them
I could put a runner on a arm-box in Amsterdam, if you tell me who to use it.
Docker supports using qemu usermode emulation, which allows any machine to (slowly) build and package the system. Erlang's JIT is not happy in this emulation, but I found the builder image for another Erlang project that has a workaround for it. That's what I'm using for my personal ARM64 Docker builds, though I believe it's using outdated Erlang and Alpine versions.
ARM releases done
will look into docker to see if it's any cleaner than the "build your own"