question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Update error message to accommodate OCI: "Registry may not support Image Manifest Version 2, Schema 2"

See original GitHub issue
Registry may not support Image Manifest Version 2, Schema 2 
at com.google.cloud.tools.jib.registry.RegistryErrorExceptionBuilder.build(RegistryErrorExceptionBuilder.java:108)
	at com.google.cloud.tools.jib.registry.ManifestPusher.handleHttpResponseException(ManifestPusher.java:119)
	at com.google.cloud.tools.jib.registry.ManifestPusher.handleHttpResponseException(ManifestPusher.java:39)
	at com.google.cloud.tools.jib.registry.RegistryEndpointCaller.call(RegistryEndpointCaller.java:258)
	at com.google.cloud.tools.jib.registry.RegistryEndpointCaller.fallBackToHttp(RegistryEndpointCaller.java:210)
	at com.google.cloud.tools.jib.registry.RegistryEndpointCaller.callWithAllowInsecureRegistryHandling(RegistryEndpointCaller.java:180)
	at com.google.cloud.tools.jib.registry.RegistryEndpointCaller.call(RegistryEndpointCaller.java:161)
	at com.google.cloud.tools.jib.registry.RegistryClient.callRegistryEndpoint(RegistryClient.java:356)
	at com.google.cloud.tools.jib.registry.RegistryClient.pushManifest(RegistryClient.java:225)
	at com.google.cloud.tools.jib.builder.steps.PushImageStep.lambda$afterAllPushed$0(PushImageStep.java:162)
	at com.google.common.util.concurrent.TrustedListenableFutureTask$TrustedFutureInterruptibleTask.runInterruptibly(TrustedListenableFutureTask.java:125)
	at com.google.common.util.concurrent.InterruptibleTask.run(InterruptibleTask.java:57)
	at com.google.common.util.concurrent.TrustedListenableFutureTask.run(TrustedListenableFutureTask.java:78)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
	at java.lang.Thread.run(Thread.java:748)
Caused by: com.google.api.client.http.HttpResponseException: 400 Bad Request
{"errors":[{"code":"MANIFEST_INVALID","message":"manifest invalid","detail":{}}]}

	at com.google.api.client.http.HttpRequest.execute(HttpRequest.java:1102)
	at com.google.cloud.tools.jib.http.Connection.send(Connection.java:200)
	at com.google.cloud.tools.jib.registry.RegistryEndpointCaller.call(RegistryEndpointCaller.java:251)
	... 12 more

Issue Analytics

  • State:closed
  • Created 4 years ago
  • Comments:12 (7 by maintainers)

github_iconTop GitHub Comments

1reaction
hendrikhalkowcommented, Apr 23, 2019

I had the same with Quay.io. It supports Docker, but not OCI format. When I have format = 'OCI' in build.gradle and try to build using gradle jib, I get the misleading message Registry may not support Image Manifest Version 2, Schema 2. With format = 'Docker' everything works fine after you are whitelisted by Quay for V2.2 support.

Can we make the error message more useful like Registry may not support Image Manifest Version 2, Schema 2 or container image format ${format}?

1reaction
chanseokohcommented, Apr 20, 2019

Registry may not support Image Manifest Version 2, Schema 2

format OCI

Perhaps you are a bit confused between the OCI manifest and the Docker Manifest V2.2.

The OCI manifest is of media type application/vnd.oci.image.manifest.v1+json, while the Docker Image Manifest Version 2, Schema 2 is of type application/vnd.docker.distribution.manifest.v2+json.

So, it could be simply that the registry does not support OCI.

What registry are you trying to build to? (For example, Docker Hub, Quay, private Harbor, etc.)

Read more comments on GitHub >

github_iconTop Results From Across the Web

Image Manifest V 2, Schema 2 - Docker Documentation
This second schema version has two primary goals. The first is to allow multi-architecture images, through a “fat manifest” which references image manifests...
Read more >
JFrog Artifactory error: Pushing Docker images with manifest ...
So I can upload the image fine to the first repository, and confirm that it is using schema 2: { "schemaVersion": 2, "mediaType":...
Read more >
Amazon ECR supports Docker Image Manifest V2, Schema 2
Amazon EC2 Container Registry (ECR) now supports Docker Image Manifest V2, Schema 2 providing the ability to assign multiple tags per image, ...
Read more >
About registries, repositories, and artifacts - Microsoft Learn
Docker Hub is an example of a public container registry that serves as a general catalog of Docker container images. Azure Container Registry...
Read more >
Artifactory Release Notes - JFrog
Fixed an issue whereby, Artifactory returned a 500 error message while resolving ... Please note that from version 7.41.2, the default value is...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found