r/embeddedlinux • u/Plastic-Swordfish-42 • Nov 26 '25
How would you implement safe OTA updates for Linux-based IoT devices (without full OS reflash)?
I’m working on an industrial IoT device running Linux (NanoPi-level SBC).
I don’t need a full A/B partition OS update solution like Mender or Balena.
What I do need to update remotely:
systemd services
Python application
networking config (static IP / Wi-Fi configs)
internal scripts + system config files under
/etc/,/usr/local/, etc.
My goal is something reliable, secure and rollback-friendly — but not heavy like full rootfs OTA.
Current thinking:
A versioned
.tar.gz“update bundle” containing files + YAML instructionsOTA agent (Python) running as a systemd service
Steps: download → checksum verify → pre-install steps → update files → restart services → post-install steps → rollback on failure
Only reboot if needed
Before I go too far — how would you architects/designers approach this?
I’m curious about:
Proven patterns or best practices
What pitfalls I should avoid
Whether there are existing lightweight tools/libraries people use
Whether packaging updates as
.debor using containers is better long-term
Not looking for “just use Mender/RAUC/Balena” — I know those options.
I’m specifically looking for meaningful advice from people who’ve deployed mid-level Linux OTA at scale.
Any discussion or architecture examples would be hugely appreciated.