Buildx: `--push` fails with `unexpected status: 404 Not Found`

[SeMeKh]

Running docker build -t myregistry.jfrog.io/backend/test --push --progress=plain . ends with:

#6 exporting to image
#6 exporting layers done
#6 exporting manifest sha256:5c7409b399a82c9db2ec67cdbd6751bbb3a3744690493d34ba7c533877d25098 0.0s done
#6 exporting config sha256:bed2be5d8b85a79ec121dc603170315afc6582b877e66d8c0053bea8ba6ccce0 done
#6 pushing layers
#6 pushing layers 0.9s done
#6 ERROR: failed commit on ref "config-sha256:bed2be5d8b85a79ec121dc603170315afc6582b877e66d8c0053bea8ba6ccce0": unexpected status: 404 Not Found
------
 > exporting to image:
------
failed to solve: rpc error: code = Unknown desc = failed commit on ref "config-sha256:bed2be5d8b85a79ec121dc603170315afc6582b877e66d8c0053bea8ba6ccce0": unexpected status: 404 Not Found

You can --push the image to DockerHub successfully, but not Artifactory's Docker registry, although docker push is successful on both registries. So, I tried to capture the network requests, and realized that there's a small difference between the way docker push and docker buildx build --push push the image layers.

Apparently, docker push does a sequence of POST, PATCH, and PUT (with no body), while docker buildx build --push does a POST followed by a PUT (with body). The latter PUT results in a 404 BLOB_UNKNOWN on Artifactory.

So, is it possible to change the behavior of docker buildx build --push to match that of docker build so that other registries work as expected? Please note that the same issue happens for --cache-to.

[tonistiigi]

cc @dmcgowan

[SeMeKh]

Any updates on this? Should this be followed up from the Artifactory team instead?

[franckOL]

Same issue. need it.
is there any kind workaround for that ?

[keiyasssss]

Same issue using latest version of builx and artifactory version 6.16.0

[Legogris]

Same issue here, with a locally hosted repository that has worked previously.

[dpipemazo]

Perhaps this issue I filed is related: #271

[opsnull]

Same issue here, with a locally hosted harbor repository.

[dathdev]

I'm running into the same issue in 2021 with Artifactory

[wichert]

@dathdev I suspect that this is related to https://www.jfrog.com/jira/browse/RTFACT-20814, which should be fixed in releases 6.20.0 and 7.5.0

[kaka-ruto]

My issue was that I was pushing to an inexistent repository (I had put the wrong url), thus my error. It worked after using the right URL

[wichert]

FYI I can confirm is that upgrading to a current version of Artifactory makes this problem go away.

[franckOL]

Since which Artifactory version it works ?

[dathdev]

I can confirm this was fixed when I upgraded Artifactory past 6.20.0.