v10.1.6-alpha — Hardened deployments get map-engine updates again; CloudTAK 13.50.0

Node-RED map-engine updates now land on security-hardened deployments

Root cause: on deployments using the strictest hardening posture — where individual certificate files are bind-mounted read-only into the Node-RED container — docker cp fails against the container (the copy trips over the read-only mount points regardless of destination), which silently aborted the automatic flow deploy. The console updated fine, but the box stayed on the previous map engine, so recent engine features (like v10.1.5's Clear Ghosts and feed lifecycle) never arrived.

Fix: the deploy now detects the blocked copy and routes file delivery through the running container instead, cleaning up any root-owned leftovers from earlier failed attempts. Non-hardened deployments are byte-for-byte unchanged — the original fast path still runs first. Saved Configurator feeds and settings are preserved through the update; config survival on the hardened posture was validated end-to-end, including a full deploy cycle.

CloudTAK 13.50.0

The vetted CloudTAK release moves to 13.50.0, validated across Ubuntu, Rocky/RHEL 9, and ARM64: update path, port hardening, database credential convergence, video stream routing, and login all verified. Boxes on the main channel pick it up through the normal CloudTAK update.

Known ARM64 caveat: CloudTAK's optional tiles service does not start on ARM64 due to an upstream dependency shipping an incompatible prebuilt binary (@mapbox/vtquery, glibc build vs musl runtime). Map, API, and all other services are unaffected. This predates this release and is tracked upstream.

Upgrade

Applied automatically on the next console update (console → Update Now). No manual steps.