ARM is a non-issue these days for the usual self-hosted stuff; most popular images ship arm64 builds (check the tags on Docker Hub before you commit to one). For a box at your mum's, I'd honestly consider staying on macOS + Docker or OrbStack rather than Asahi, purely because remote fixes are easier when the OS is the boring one. Add Tailscale so you can reach it without opening ports. 8 GB is plenty for things like a photo backup, an ad blocker, or a small search engine like SearXNG; it's tight only if you try to run local LLMs on it.
post
have had nothing but a stellar experience with asahi.
I was bummed when I had to upgrade; but, they are close to an m3 release any day now...
Most things should work just fine. There's not all that much that requires x86.
So the real question is, what does your mom need/want? NextCloud? Jellyfin media server? Ente photos?
Maybe just a media center? Basically an Apple TV on crack?
Yeah, it was mostly to try to relieve her phone storage of all the screen shots she takes and doesn't want to get rid of. She takes a ton of photos and we don't want to keep paying for an iCloud sub if we have the means to do it ourselves.
for that, Immich is pretty much made for it. the phone app can back up automatically and it's the closest thing to Google/iCloud Photos you can host. it has arm64 images and the docs say 6GB RAM minimum, 8 recommended, so a base M1 is fine for one person. one Asahi gotcha: it uses 16K memory pages, and a few arm containers built with older jemalloc crash with "Unsupported system page size" (some Immich postgres tags did this on the Pi 5). the current default compose file is fine, just don't copy an old pinned database image from a random guide.
all 14 comments