harbor: Using buildkit exporting cache reporting status: 404 Not Found

This is still very relevant. Would there be any news about this?

Uping this one.

Any update on this? How could I help ?

If any one want to fix:

diff --git a/src/controller/artifact/abstractor.go b/src/controller/artifact/abstractor.go
index 233008157..5df41b2cd 100644
--- a/src/controller/artifact/abstractor.go
+++ b/src/controller/artifact/abstractor.go
@@ -160,6 +160,15 @@ func (a *abstractor) abstractIndexMetadata(ctx context.Context, art *artifact.Ar
 	// populate the referenced artifacts
 	for _, mani := range index.Manifests {
 		digest := mani.Digest.String()
+
+		// Buildx can reference layer in manifest
+		// see: https://github.com/docker/buildx/issues/173#issuecomment-873152302
+		switch mani.MediaType {
+		case v1.MediaTypeImageLayer, v1.MediaTypeImageLayerGzip, v1.MediaTypeImageLayerNonDistributable, v1.MediaTypeImageLayerNonDistributableGzip, "application/vnd.buildkit.cacheconfig.v0":
+			art.Size += mani.Size
+			continue
+		}
+
 		// make sure the child artifact exist
 		ar, err := a.artMgr.GetByDigest(ctx, art.RepositoryName, digest)
 		if err != nil {

Then you can rebuild the images with make compile build

I don’t know the side effect on garbage collection tho.

Hi, we would be interested by news about this as well, this is crucial for Production grade build capability with Harbor and buildkit. Alternately, has anyone used a separate generic repo exclusively for caching as a workaround? (when not using Github actions)

Any updates here?

Any news on this one? It’s still an issue on v2.5.

+1 Same issue to me.

#18 ERROR: error writing manifest blob: failed commit on ref “sha256:b0b8b156437e48583181a25ad6fecc5cfa45152005d47e215e824202e6cb579c”: unexpected status: 404 Not Found

Here is what I found on my gateway:

“PUT /v2/project/repo/manifests/buildcache HTTP/1.1” 404

harbor version: 2.3.2 docker engine version: 20.10.8+azure buildkit: github.com/moby/buildkit v0.9.0

@prosnekov as mentioned in https://github.com/goharbor/harbor/pull/18105, you can provide image-manifest=true: --export-cache type=registry,mode=max,image-manifest=true,ref=$CACHE_IMAGE

However, the option is only available for buildkit:master (which afaik is not stable), and not yet for buildkit:latest.

Having the same issue here. Is there any update on this?

Uping this one.

Any update on this? How could I help ?

still an issue for harbor 2.6.1

Running into this issue as well, is this fixed in a recent version, or is it still in the backlog?

we are still there. i’m wondering if it’s not less work to fix it than do some triage every week on the issue since 2 years …

@XciD i also took the time that artifacts are well cleaned up upon GC, and seems everything is OK.

I did some investigation around this issue, if you use --cache-to "type=registry,mode=max,ref=registry.... it will end up trying to uploaf manufest of type application/vnd.buildkit.cacheconfig.v0 which is not supported by all registry implementation, I think harbor does not support it?

I found this in logs of buildx docker instance:

time="2022-08-25T23:49:30Z" level=warning msg="reference for unknown type: application/vnd.buildkit.cacheconfig.v0"
time="2022-08-25T23:49:31Z" level=error msg="/moby.buildkit.v1.Control/Solve returned error: rpc error: code = Unknown desc = error writing manifest blob: failed commit on ref \"sha256:bd239a08c4b36bbc2397ea00826c1dd34c53ffbdf751685c4ae2955e631e1b81\": unexpected status: 404 Not Found\n"
time="2022-08-25T23:57:44Z" level=warning msg="reference for unknown type: application/vnd.buildkit.cacheconfig.v0"
time="2022-08-25T23:57:45Z" level=error msg="/moby.buildkit.v1.Control/Solve returned error: rpc error: code = Unknown desc = error writing manifest blob: failed commit on ref \"sha256:bd239a08c4b36bbc2397ea00826c1dd34c53ffbdf751685c4ae2955e631e1b81\": unexpected status: 404 Not Found\n"
time="2022-08-26T01:00:35Z" level=warning msg="reference for unknown type: application/vnd.buildkit.cacheconfig.v0"
time="2022-08-26T01:00:36Z" level=error msg="/moby.buildkit.v1.Control/Solve returned error: rpc error: code = Unknown desc = error writing manifest blob: failed commit on ref \"sha256:bd239a08c4b36bbc2397ea00826c1dd34c53ffbdf751685c4ae2955e631e1b81\": unexpected status: 404 Not Found\n"
time="2022-08-26T01:03:00Z" level=info msg="stopping server"
buildkitd: context canceled

can someone with knowledge confirm the support for application/vnd.buildkit.cacheconfig.v0 media type?

inline cache is probably good workaround: https://github.com/moby/buildkit#inline-push-image-and-cache-together