The latest bink disk image with the tag v1.35-fedora-44-disk doesn't reference an existing node image

[alicefr]

The make deploy-bink in the bootc-operato still pulls the image by tag and the latest is failing with

 make deploy-bink 
bink registry start
podman pull ghcr.io/bootc-dev/bink/node:v1.35-fedora-44-disk
Trying to pull ghcr.io/bootc-dev/bink/node:v1.35-fedora-44-disk...
Getting image source signatures
Copying blob 6cd236f7f9a0 done   | 
Copying blob f415c52fc685 done   | 
Copying config 41c617fd94 done   | 
Writing manifest to image destination
41c617fd94921594658d71aa44bde97e8282d5da7260f6a6e02d8699af01dc61
bootc_img=$(podman inspect --format '{{index .Config.Labels "bink.bootc-image"}}' ghcr.io/bootc-dev/bink/node:v1.35-fedora-44-disk) && \
	bootc_digest=$(podman inspect --format '{{index .Config.Labels "bink.bootc-image-digest"}}' ghcr.io/bootc-dev/bink/node:v1.35-fedora-44-disk) && \
	podman pull "$bootc_img@$bootc_digest" && \
	podman tag "$bootc_img@$bootc_digest" localhost:5000/node:latest
Trying to pull ghcr.io/bootc-dev/bink/node@sha256:a77a746898d8c5140f145a079cc7235bb46b90f2951b60babca8964b5a7a031d...
Error: unable to copy from source docker://ghcr.io/bootc-dev/bink/node@sha256:a77a746898d8c5140f145a079cc7235bb46b90f2951b60babca8964b5a7a031d: initializing source docker://ghcr.io/bootc-dev/bink/node@sha256:a77a746898d8c5140f145a079cc7235bb46b90f2951b60babca8964b5a7a031d: reading manifest sha256:a77a746898d8c5140f145a079cc7235bb46b90f2951b60babca8964b5a7a031d in ghcr.io/bootc-dev/bink/node: manifest unknown

If you inspect:

$  podman inspect --format '{{json .Config.Labels}}' ghcr.io/bootc-dev/bink/node:v1.35-fedora-44-disk | jq
{
  "bink.bootc-image": "ghcr.io/bootc-dev/bink/node:v1.35-fedora-44",
  "bink.bootc-image-digest": "sha256:a77a746898d8c5140f145a079cc7235bb46b90f2951b60babca8964b5a7a031d",
  "bink.kubeadm-version": "1.35",
  "io.buildah.version": "1.33.7"
}
$ podman pull ghcr.io/bootc-dev/bink/node@sha256:a77a746898d8c5140f145a079cc7235bb46b90f2951b60babca8964b5a7a031d
Trying to pull ghcr.io/bootc-dev/bink/node@sha256:a77a746898d8c5140f145a079cc7235bb46b90f2951b60babca8964b5a7a031d...
Error: unable to copy from source docker://ghcr.io/bootc-dev/bink/node@sha256:a77a746898d8c5140f145a079cc7235bb46b90f2951b60babca8964b5a7a031d: initializing source docker://ghcr.io/bootc-dev/bink/node@sha256:a77a746898d8c5140f145a079cc7235bb46b90f2951b60babca8964b5a7a031d: reading manifest sha256:a77a746898d8c5140f145a079cc7235bb46b90f2951b60babca8964b5a7a031d in ghcr.io/bootc-dev/bink/node: manifest unknown

Something we wrong with the latest build

[alicefr]

Latest build also have this problem, see: https://github.com/bootc-dev/bink/actions/runs/34602092288/job/103271681713

[alicefr]

The workaround about this is to use the same image bootc-operator CI uses, it can be set with:

export BINK_NODE_DISK_IMAGE=ghcr.io/bootc-dev/bink/node@sha256:3195dd85fdc2f03cf0e50f655f19a1baf569f7f8fbcaf1756ba62108580d5867