feat: inspect-image reads what a game's image needs #2

Merged

greg merged 2 commits from feat/inspect-image into main 2026-10-25 07:06:11 +00:00

Conversation 2 Commits 2 Files Changed 8

+1563 -1

2 Commits

Author	SHA1	Message	Date
gregandClaude Opus 5.5	c9d9cd6ff5	feat: first-boot records what a server does with no settings ... `gbrgames first-boot -game <id>` (or -image for a game with no template) starts the server once like the node-agent does (same volumes, user, SteamCMD install and startup prefix) but with none of the template's settings and no restart policy, in the isolated gbr-boottest network. It watches the console until the server exits, goes quiet or hits -max, stops it gracefully (many servers write their settings on shutdown) and records: - the console with timings, plus ready and error lines; the last strong ready line before the stop becomes a readyPattern / readyExample pair - every file created; config files are copied out and parsed into settings with their defaults (INI, properties, JSON, YAML, Unreal OptionSettings=(...) lists); log files are scanned for ready lines too - files written outside the volumes, which a recreated container loses Minecraft: ready line `Done \([0-9.]+s\)! For help, type "help"` and 76 settings (69 from server.properties) found with no template input. ARK: showed its image retries nothing when SteamCMD fails with "Missing configuration" and starts a server that was never installed. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-10-25 02:18:21 -04:00
gregandClaude Opus 5.5	40e7372dab	feat: inspect-image reads what a game's image needs ... `gbrgames inspect-image -game <id>` pulls the image and reads, without starting the game (probe runs with --network none and bypasses the entrypoint): its user, accounts, home folder owners and modes, tools (java, steamcmd, proton...), startup scripts and the variables they read. It then checks the template against those facts: - an image built around its own user (a locked home owned by another uid, or a declared USER) needs a matching containerUser - the startup command must read settings under the names the node gives them (the agent's toUpperSnakeCase), and must not read unset variables that have no default On the template from the first commit it reports both ARK bugs found by boot tests today (uid 25000; ${RCON_PORT} vs RCONPORT); the current five templates pass. Boot tests now run it first, so such templates fail in seconds instead of after a boot. -json prints the facts for tooling. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-10-25 01:42:55 -04:00