lfg2025/archy
1
0
Fork 0
Code Issues 11 Pull Requests Actions Packages Projects Releases 12 Wiki Activity

Pin node-only V4V demo to verified registry image

Browse Source
This commit is contained in:
archipelago
2026-10-06 04:13:08 -04:00
parent 69cd4021f2
commit a94b9c64aa
2 changed files with 23 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
demos/node-demo-v4v/manifest.yml
+1 -1
View File
@@ -7,7 +7,7 @@ app:
description: Listen to the original V4V demo catalog and explore sovereign music on this node.
category: media
container:
image: source.archipelago-foundation.org/lfg2025/v4v-demo:0.6.7-alpha-archy1
image: source.archipelago-foundation.org/chaum/v4v-demo:0.6.7-alpha-archy1@sha256:13044ecbeae9eb17bc98cc531ca202db9e9a0db8dc2ce01bb9f8cb789248d020
generated_secrets:
- name: node-demo-v4v-session
kind: hex32
docs/node-demo-catalog-and-media.md
+22
View File
@@ -82,3 +82,25 @@ origin/nonce rejection, locked controls and removal of metadata after relocking.
The isolated container reached HTTP health 200, then exposed the management
reaper's separate-storage ownership bug. Runtime acceptance is blocked on its
tested deployment; the old V4V image and live Portainer volumes are untouched.
## Registry qualification — 2026-10-06
The node-only manifest now pins the staged image by immutable digest:
`sha256:13044ecbeae9eb17bc98cc531ca202db9e9a0db8dc2ce01bb9f8cb789248d020`.
The registry namespace is `chaum/v4v-demo`, where the publisher has package write
access. This does not publish an app catalog entry.
Anonymous registry access verified the raw manifest digest and raw Docker
configuration blob. Its configuration digest matches the qualified local image,
`sha256:cd56bef6ec2c9d5d56b41d370c735fc3b4c12885acb1530be75c79a5dbde923f`.
The raw blob retains the Node `/healthz` probe, 30-second interval, 3-second
timeout, 10-second start period and three retries. `skopeo inspect --config`
normalizes this configuration and omits the Docker Healthcheck field; therefore
that output alone must not be used to decide whether this image retains it.
The accepted push explicitly used Docker v2 schema 2 format.
This is registry verification, not managed-install acceptance. Root-signed
node catalog, copied-data installation, lifecycle checks, physical companion
checks and final dashboard cold-launch regression remain required. Deployment
writes to dev and Yaya are paused because another session installed a mining
candidate on both nodes; reconcile source before replacing either build.