fix: align ContainerInfo fields with inspect format template#11
Merged
Conversation
hectorvent
approved these changes
Jun 30, 2026
8 tasks
hectorvent
added a commit
that referenced
this pull request
Jul 7, 2026
…elf-update (#14) * docs: add AGENTS.md, CONTRIBUTING.md, PR template; document GCP and self-update - AGENTS.md (tracked): canonical agent guidance — architecture incl. the three product trees table, doctor check structure per tree, native-image constraints, code style rules, updated scope rules (self-update now in scope, must never auto-run) - CONTRIBUTING.md: build/test setup, Conventional Commits, hand-maintained Keep-a-Changelog policy, PR guidelines, tag-driven release process - .github/pull_request_template.md: adapted from the server repo with a 'product trees affected' checklist - README: document the floci gcp command group (quick start, command reference, global flags, gcp env variables, CI usage), floci update, Java 25+ fat-JAR requirement; drop the unwired snapshot --message flag from examples - CHANGELOG: backfill [Unreleased] with #12 (self-update) and #11 (ContainerInfo field alignment); document these docs changes - release.yml: release notes said the fat JAR needs Java 21+, but it is built with --release 25 — corrected to Java 25+ * docs(changelog): use standard Keep a Changelog headings for Unreleased The Documentation section is not one of the six types defined by Keep a Changelog 1.1.0. New docs (AGENTS.md, CONTRIBUTING.md, README GCP section) move under Added; the incorrect Java 21+ runtime claim moves under Fixed.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
floci starttreated a running container as stopped and then failed trying to remove it:The root cause was a field-mapping bug in
inspectContainer. Thedocker inspectformat template emitted a duplicate{{.State.Status}}, producing 6 fields while the data only had 5. Every field after the image was off by one, sostatusended up mapped to the ports slot. As a resultstate()returned the wrong value, never matched"running", and the start flow attempted todocker rma live container.Separately, the command used
docker inspect(no subcommand), which falls back to images when no container matches. With an image namedflocipresent, the template rendered against the image and failed at{{.Name}}:template parsing error: executing "" at <.Name>: map has no entry for key "Name"Fix
docker container inspectNo such containerinstead of rendering against an image{{.State.Status}}id,name,image,state,portsContainerInfoconstructorparts[0..4];state→parts[3],ports→parts[4]Optional.empty()Verification
mvn test).inspectContainerreturns the correctstatefor running, stopped, and missing containers.