MakeKeeper 0.18.2: the images run natively on ARM
MakeKeeper 0.18.2 went out on 13 September 2026, and it contains no application changes whatsoever. It matters anyway, because of who can now run the product at all.
The machine your workshop already has
The computer that ends up hosting a workshop tool is rarely a server. It is the Pi on the shelf that already runs the 3D printer’s camera, or the cheapest VPS that would take a Docker install — and for a couple of years now, both of those have quietly been ARM machines.
MakeKeeper was the awkward guest on them. The published images were linux/amd64 only, so an ARM
host either emulated an x86 build — slower, hungrier, odd under load — or, where no emulation was
configured, simply failed to start with a message about the wrong architecture. The site said the
app runs on a Raspberry Pi. On a good day, with binfmt set up, it did.
Same tag, native build
Every tag — 0.18.2, 0.18 and latest — is now published for linux/amd64 and
linux/arm64. A Raspberry Pi on a 64-bit OS, an Ampere or Graviton VPS, an Apple Silicon machine
pulls the build that matches it.
Nothing about installing or updating changes. The tag is the same, the installer is the same one command, and Docker picks the right image on its own:
curl -fsSL https://raw.githubusercontent.com/makekeeper/makekeeper/main/deploy/install.sh | bashIf you are already running on ARM under emulation, an ordinary update is enough — the next pull brings down the native build.
The optional MCP plugin image is not part of this release. It has its own version line, and its next release will carry both architectures as well.
Nothing else changed
There are no application changes in 0.18.2. It exists so that the ARM images reach you: support for
an architecture arrives only with a tag. An x86 install updating to 0.18.2 gets a functionally
identical build of 0.18.1 — same features, same fixes, same behaviour. If you are on x86, there is
nothing here for you, and that is the honest version of this note.
What is not published
Other architectures — 32-bit ARM, RISC-V — are not published. If your host until now pulled the x86 image and emulated it, it will no longer find a matching image. That is the one way this release can make things worse rather than better, so it is worth saying plainly: an older Pi running a 32-bit OS needs a 64-bit one, and RISC-V boards are not covered.
Under the hood
Release images are now built by GitHub Actions from the published source snapshot. An image is therefore provably built from the code in the public repository, rather than merely claimed to match it — which is the point of publishing the source in the first place.
Next: 0.19 — the label goes straight onto the drawer. Previously: 0.18 — the first five minutes. Still free, still yours, still one command to install.