Two things, both found by running the driver for the first time rather than by reading it. The fields came out shifted. recipes.py separated them with tabs, and bash's `read` treats tab as IFS whitespace, so two in a row are one delimiter - which meant an application with no upstream image, that being most of them, lost a column and everything after it moved left. The build took the binary list as the upstream reference and the status as the binary list, and failed with "image is missing available". An awk -F'\t' check of the same output had looked perfectly correct, because awk does not collapse. The separator is now \x1f, which is not whitespace in anybody's reading. And a push does not need a token handed to it. The control plane has kept a registry login in the service account's REGISTRY_AUTH_FILE since the node image was first published, so demanding the secret again meant fetching one that was already on the machine and putting it in a shell history to do it. The driver uses the stored login when there is no token, and says which it used. stress-ng is published as OCI, because there is no Apptainer here to convert it - so the head does that on arrival and the entry carries no SIF hash. The catalogue records the reference that was actually pushed rather than the one the recipe would have produced, which is why docker:// and oras:// sit side by side in it and both resolve. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
8 lines
141 B
JSON
8 lines
141 B
JSON
{
|
|
"stress-ng:0.18.07": {
|
|
"digest": "",
|
|
"image": "docker://gitea.mynodes.xyz/hpcapps/stress-ng:0.18.07",
|
|
"sif_sha256": ""
|
|
}
|
|
}
|