SBOM Attestations seem to cause intermittent: 416 Requested Range Not Satisfiable when pushing

[jabbera]

Describe the bug
Ever since we added --attest type=sbom,generator=docker/scout-sbom-indexer:latest to our docker build we are getting random 416 errors when we are pushing our image or the cache. The SBOM is very large (92 MB json)

We also push cache layers with --cache-to. Image size is roughly 10GB

I don't have first party Microsoft support so a ticket isn't something I'm willing to open currently but I'm happy to communicate details. If there is commitment from MSFT to pickup the ticket I'm happy to open one.

To Reproduce
1.Build large image with SBOM attestation.

Expected behavior
No intermittent error.

Screenshots
Error message:

ERROR: failed to build: failed to solve: failed to push <SNIP>.azurecr.io/nre/temp/jupyter/<SNIP>-pytorch-notebook:pr55652: unexpected status from PUT request to https://<SNIP>.azurecr.io/v2/nre/temp/jupyter/<SNIP>-pytorch-notebook/blobs/uploads/a94f5e86-86e9-49e1-ba27-6ab39655a2b8?_nouploadcache=false&_state=8joUEnWY2MnZRhHwRukugxPJaXTrP0wRzsE4-R8bx3h7Ik5hbWUiOiJucmUvdGVtcC9qdXB5dGVyL2dtby1weXRvcmNoLW5vdGVib29rIiwiVVVJRCI6ImE5NGY1ZTg2LTg2ZTktNDllMS1iYTI3LTZhYjM5NjU1YTJiOCIsIk9mZnNldCI6MCwiU3RhcnRlZEF0IjoiMjAyNi0wMi0wNVQxOTozMDoxMy4zMDUzODYxNDRaIn0%3D&digest=sha256%3A77afaa97898b53372408aa44a6471670e84bd3f983e30f66889f30724e59c623: 416 Requested Range Not Satisfiable

Any relevant environment information

• Docker version: Whatever is on the Azure Devops Pipeline agents
• Datetime (UTC) when the issue occurred: 2026-02-05T19:30:29.8803538Z
• Registry and image names

Additional context
Add any other context about the problem here.

If any information is a concern to post here, you can create a support ticket or send an email to acrsup@microsoft.com.

[terencet-dev]

Hi @jabbera, just to confirm you are unable to open a support ticket for this?

[jabbera]

Hi @jabbera, just to confirm you are unable to open a support ticket for this?

@terencet-dev I can but not directly with Microsoft. We have third party support as a frontline so it takes a ton of pushing to get a ticket over to the MSFT side. If I had an employee at MSFT asking me to open the ticket and to have it escalated I'm happy to do it.