I’ve got a mix of architectures in my basement cluster - some Odroid HC2s that are arm7, some Raspberry Pi 4s that are arm64, and am soon going to add an Intel node as well. It’s more hassle than it’s worth to have to specify different images for the different architectures. I already build my own copies of images, so I decided to start building all my images as multiarchitecture images. ...
Do not use duplicacy! TL;DR: duplicacy is unusable if you’re serious about backing up your data. Use restic instead! I wanted to ensure any data I put into my ARM k3s cluster is backed up to prevent data loss. I no longer recommend duplicacy. Instead, read my article on restic backups on TrueNas instead. 2025 edit: This post is only here for historical reasons. Do NOT use duplicacy. It does not report backup errors in its exit code. You will have to parse its logs yourself and hope your regex didn’t miss an error condition. And every update, you’ll have to check and make sure it hasn’t changed anything that your regex was catching. Backups are supposed to be something you set up once and ignore other than to do periodic restore tests, and duplicacy fails that simple criteria. ...
I had a bunch of cruft in start scripts that would determine the IP of my laptop and set it as an environment variable to pass to docker-compose and it turns out that with Docker for Mac you don’t have to do all that work - just use docker.for.mac.localhost as a hostname.