Repository navigation
release: 0.9.0 — the quickstart points at the loop whose recovery says what it could not establish - #26
Merged
Conversation
…s what it could not establish The six image lines move from 0.8.1 to 0.9.0, pinned by the OCI index digests GHCR serves for the tags, read anonymously after the release run for the tag finished green on every job; :latest carries the same four. Nothing in 0.9.0 is something this file depends on, so the comment keeps saying it needs 0.8.0 or newer and points at the newest. The only compose key added since 0.8.1 is the lease length, left at its default here. Run the way a stranger does, from an empty directory: pulled by digest, boards up, the demo's nine steps with the press executed and demo exit 0, down -v. Read back from the running images: the investigator's posture is no-credentials with the metadata question asked and answered no; the probe is in the image; the pipe's lease is 120 seconds. Rollback: re-pin to the 0.8.1 digests; 0.8.1 ignores the pending_signatures table.
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.
The quickstart's six image lines move from 0.8.1 to 0.9.0, pinned by digest as
docs/releasing.mdsays. The digests are the OCI index digests GHCR serves for the0.9.0tags, read anonymously after the release run for the tag finished green on every job;:latestcarries the same four.Nothing in 0.9.0 is something this file depends on, so its comment keeps saying it needs 0.8.0 or newer and points at the newest. The only compose key added since 0.8.1 is
HOOKRELAY_SIGNATURE_LEASE_SECONDS, which the quickstart leaves at its default.Run the way a stranger does before this was opened, from an empty directory holding only the compose file and
scripts/demo.sh: pulled by digest, the three boards answered200within seconds, and the demo ran all nine steps (routes ai 2, reuse 1, recovery 1; the card press executed both observations; the recovery verified the work).demo exit=0;down -vremoved the containers, the volumes and the network.Read back from the running images: the investigator's posture is
no-credentials, with the instance-metadata question asked and answered no on this machine; the new probe is in the image; the pipe's lease length is 120 seconds.Upgrading note for strangers on a cloud VM: if the instance metadata service offers a role to containers, the quickstart's readonly investigator, which has no
awsCLI, now refuses to start under the defaultenforce. The tag note lists the ways out.Rollback: re-pin these lines to the 0.8.1 digests; the pipe's new
pending_signaturestable is ignored by 0.8.1.Gate: STACK GATE GREEN locally; CI read back before merging.