Help

Compatibility

What we have tested, and how.

Tested with the production installer and agent:

PlatformHow it was tested
amd64, systemdReal hardware
Debian 12, Ubuntu 24.04, Arch, Fedora 41, openSUSE Leap 15.6Installer and agent in containers
Alpine 3.20 (BusyBox, wget, OpenRC)Installer, agent and supervised OpenRC service
arm64, armv7, armv6Full end-to-end suite under emulation
386Full end-to-end suite, natively
Raspberry Pi OS Lite 13 (trixie), 64-bit and 32-bit, October 2026 imagesOfficial image's root filesystem under ARM emulation: installer, enrollment, fleet command, inventory (dpkg), uninstall
Yocto 5.0 (Poky core-image-minimal and core-image-full-cmdline, qemuarm64)Same, with BusyBox wget and sysvinit: the agent is registered in /etc/inittab and restarted by init
OpenWrt 25.12.6 (x86-64, official image)In a VM: wget installer, enrollment, procd service, back online after reboot, restarted after a kill, uninstall

Emulation runs the real userland (libraries, BusyBox, package database, init configuration) but not the board: Pi temperature sensors, SD cards and cellular modems are still unverified on real hardware. Buildroot is expected to work the same way as Yocto. OpenWrt routers need an amd64, arm64 or armv7 CPU (no MIPS build yet). If you run one, tell us how it went at support@fieldhand.dev and we'll list it here.

BusyBox wget (Yocto and Buildroot minimal images) connects over HTTPS but doesn't check the server's certificate, so the download trusts the network it runs on. On images without curl, install from a network you trust, or bake curl into the image. Updates after install are always checked against our release signature.

Not supported: Windows, macOS, and Linux without a /dev/ptmx (very old or very stripped kernels).

Something wrong or missing on this page? Tell us.