fix(a113d): start the console with --serve in /init

The A113D image boots a custom /init (not BusyBox rcS, so the init.d overlay is
not run). That /init launched the console binary with no args, which only
prints usage -- so the board came up on SSH + network but served no web UI/API.
Patch /init during the build to launch 'alkane-os --serve', bringing up the
web console on :80 and the HTTP API that fleet discovery/install-verify need.
Caught by the full GUI-flow test (board installed + reachable but absent from
the post-install scan).

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01B1W6qKwKxq3oUPDKWicM6i
This commit is contained in:
2026-11-17 15:23:21 -06:00
co-authored by Claude Opus 4.8
parent 55715492b0
commit 5304105c61
+7
View File
@@ -70,6 +70,13 @@ mkdir -p "$RFS"
install -D -m 0755 "$WORK/alkane-os" "$RFS/usr/bin/alkane-os"
# The .afw version, reported by GET /api/identity (fleet discovery).
printf '%s\n' "$VERSION" > "$RFS/etc/alkane-os-version"
# This board boots a custom /init (not BusyBox rcS, so the init.d overlay is not
# run). That /init launches the console binary with no args -- which only prints
# usage and exits. The real binary needs `--serve` to bring up the web console +
# HTTP API, so patch the launch line. Idempotent.
if [ -f "$RFS/init" ] && ! grep -q 'alkane-os --serve' "$RFS/init"; then
sed -i 's#\(/usr/bin/alkane-os\)\( >/dev/null\)#\1 --serve\2#' "$RFS/init"
fi
if [ -d "$OVERLAY" ]; then
( cd "$OVERLAY" && find . -type f ) | while IFS= read -r f; do
install -D -m 0755 "$OVERLAY/${f#./}" "$RFS/${f#./}"