balena deploy suddenly fails due to "... was found but does not provide any platform"

Product support
1

I have an azure devops pipeline that deploys to balena using balena deploy with pre-build images. But today the pipeline gives (multiple of) these errors:

Retrying "registry2.balena-cloud.com/v2/a98f703c57a0dff8e320d928f688b278:latest" after 2.0s (1 of 2) due to: Error: image with reference registry2.balena-cloud.com/v2/a98f703c57a0dff8e320d928f688b278:latest was found but does not provide any platform

When I deploy manually I don’t have this problem.

I’ve tried to update the balena CLI but the issue persists. Any pointer how to solve this issue?

2

Root Cause:
Microsoft upgraded Docker on Azure Pipelines hosted agents from 28.x to 29.1.5 (announcement). Docker 29.1.x outputs images in OCI Image Index v1 format by default, which Balena’s registry cannot parse for platform metadata.

Workaround:
Downgrade Docker to 28.0.4 before building/pushing images.

Related Issues:

This is not a Balena CLI issue - upgrading to v23.2.32 doesn’t fix it. The downgrade resolves deployments immediately.

Not sure if this can somehow be fixed on Balena’s side. Would appreciate any other input.

3

I can indeed confirm that rolling back docker in our azure pipeline resolves the issue. So let’s wait for a fix on the balena cloud’s side