Failed getting image: More than one match for the provided partial fingerprint

I am trying to launch images:nixos/unstable container, but getting today:

Error: Failed instance creation: Failed getting remote image info: Failed getting image: More than one match for the provided partial fingerprint

First time I see such error to be honest, are there any troubles with images generator?

@adamcstephens looks like more fallout from the publishing change for NixOS?

They appear to be publishing fine, but the image server does indeed report multiple images with the same fingerprint and incus launch apparently treats that as fatal. Could that be considered a bug on the incus side?

We don’t rebuild images every day, it’s usually every few days. This means pulling the image daily can yield duplicate images. This wasn’t a problem before because the distrobuilder repack must have an impurity (e.g. the date) which causes the image to get a new fingerprint on repack.

𑁱 incus image list images: type=container architecture=x86_64 | rg Nixos\ unstable
| nixos/unstable/amd64 (1 more)      | e88a155b2020 | yes    | Nixos unstable amd64 (20251222_01:01)      | x86_64       | CONTAINER | 245.65MiB | 2025/12/22 00:00 UTC |
|                                    | bbf0a43634bb | yes    | Nixos unstable amd64 (20251216_01:03)      | x86_64       | CONTAINER | 245.59MiB | 2025/12/16 00:00 UTC |
|                                    | e88a155b2020 | yes    | Nixos unstable amd64 (20251221_02:02)      | x86_64       | CONTAINER | 245.65MiB | 2025/12/21 00:00 UTC |

I’m open to suggestions here @stgraber. Some ideas I have are trying to detect/skip if it’s already on the image server, preventing the image server from accepting/serving duplicate fingerprints, patching incus to gracefully handle this, or rolling back to distrobuilder?

A workaround would be to launch nixos/25.11 images for now until we can get unstable fixed, as stable releases are not impacted. If you still want unstable, update channels/inputs as desired and nixos-rebuild.

1 Like

We may need to add a bit of logic to the publishing script so it refuses to publish a second copy of the same fingerprint.

I think we should be good now

2 Likes

Thanks for the quick fix!