[BUG]: DockerV2 push broken after upgrade to Docker 29

[escherstair]

New issue checklist

• I searched for existing GitHub issues
• I read pipeline troubleshooting guide
• I checked how to collect logs

Task name

DockerV2

Task version

2.172.0

Issue Description

The upgrade to Docker V29 actions/runner-images#13474 broke the behavior of DockerV2 push.
As reported in this issue moby/moby#51532 now docker push pushes an OCI image manifest instead of a single image as in the past.

And so the behavior of DockerV2 push changed too in the same way.
And this broke my CI.

I found some workaorunds (downgraging Docker, use alternatives to DockerV2, ...) but I think that behavior of DockerV2 should be restored (or a new parameter to restore the old behavior when needed).

Environment type (Please select at least one enviroment where you face this issue)

• Self-Hosted
• Microsoft Hosted
• VMSS Pool
• Container

Azure DevOps Server type

dev.azure.com (formerly visualstudio.com)

Azure DevOps Server Version (if applicable)

No response

Operation system

Ubuntu 24.04

Relevant log output

it's not an error in the pushing.
It's a chnage in what is pushed.
Media type:
application/vnd.oci.image.manifest.v1+json
instead of
application/vnd.docker.distribution.manifest.v2+json

Full task logs with system.debug enabled

Details

Repro steps

[MarcusKohnert]

@escherstair Thanks for your investigation. We also suddenly have issues pushing images to a registry without changing anything.

How did you find out about the media type change? How did you log that media type?

[escherstair]

@MarcusKohnert when I saw that we started having issues without any change from our side I searched something on Azure DevOps infrastracture and I see this.
Then I saw this one too.

You can log the storage type running docker info command in the pipeline as I wrote in my message here.
If you mean the Media type, I see this in the web page of Azure Container Registry.

In any case, this workaround seems ok (at the moment) on MS-hosted Ubuntu 24.04.
I don't know on other scenarios.

[MarcusKohnert]

Thank you so much @escherstair for the detailed explanation. The workaround (explicitly defining the platform) works in my scenario. Here is what I've changed in my azure pipeline.

Changes:

• Docker@V2 buildAndPush can not work with arguments
• So I split build and push into two tasks
• The push task gets: arguments: --platform linux/amd64 # https://github.com/moby/moby/issues/51532

docker push now works again.

[MartenM]

Faced the same issue. An external registry cannot handle the newer image format from OCI so this started breaking our pipelines. The upgrade to the image runners resulted in the media type application/vnd.oci.image.index.v1+json.

In any case, actions/runner-images#13474 (comment) seems ok (at the moment) on MS-hosted Ubuntu 24.04.
I don't know on other scenarios.
arguments: --platform linux/amd64

I used both of these fixes and the image manifest is now back to being application/vnd.docker.distribution.manifest.v2+json.