carlos / platform Public

Plan 1 Task 11: carlos ship --check against real podman (DOCS-T1) Question open

On branch rootfs-apps-1-ship

Recorded as the brief asks (rootfs Plan 1 Task 11 step 5). Rootless podman 5.4.2 on DOCS-T1 (amd64, no arm64 binfmt), static carlos built in scratch, CARLOSCHECKPROBE unset (self-probe):

  1. arm64 static server from a directory: C60, C61, then C70 quoting crun's "Exec format error" — a real bug: crun capitalises it. Fixed (case-insensitive match + a test with crun's exact line); re-run gave C60, C61, C62, C75.
  2. amd64 static unix-socket server in an image imported with --arch arm64 (runs natively): C60, C61, "web answered GET / with 200 after 0.0 s", C74, exit 0. Proves the in-container probe exec, the socket on the uid-65534 tmpfs volume, read-only root, the 1 GiB memory flags.
  3. Same server listening on 127.0.0.1:3000 instead of the socket: C68 after the 120 s bound, C75, exit 1. Proves the /proc/net/tcp read.

After each run no carlos-check-* container, volume or image remained; the two test images were removed. Not run: Docker, macOS (Docker Desktop VM), real arm64. Review fix round 1 (env via -e KEY instead of env files; cleanup errors reported) follows.