pushing to Quay fails #698

warmuuh · 2018-07-24T06:50:05Z

Description of the issue:

if pushing an image to Quay v2.9.1, it responds with

HttpResponseException: 415 Unsupported Media Type
{"errors":[{"code":"MANIFEST_INVALID","detail":{"message":"manifest schema version not supported"},"message":"manifest invalid"}]}

Expected behavior:

push of image should be successful

Steps to reproduce:

running mvn compile jib:build on a project with jib-plugin

Environment:

Apache Maven 3.5.3
Java version: 1.8.0_171, vendor: Oracle Corporation
OS name: "windows 10", version: "10.0", arch: "amd64", family: "windows"
Docker version 18.03.1-ce (using windows hyper-v)
Quay v2.9.1

jib-maven-plugin Configuration

			<plugin>
				<groupId>com.google.cloud.tools</groupId>
				<artifactId>jib-maven-plugin</artifactId>
				<version>0.9.7</version>
				<configuration>
					<to>
						<image>{quay-registry}/{userId}/{project}</image>
					</to>
				</configuration>
			</plugin>

Log output:

org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal com.google.cloud.tools:jib-maven-plugin:0.9.7:build (default-cli) on project wall-e: Build image failed
    at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:213)
    at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:154)
    at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:146)
    at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:117)
    at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:81)
    at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build (SingleThreadedBuilder.java:56)
    at org.apache.maven.lifecycle.internal.LifecycleStarter.execute (LifecycleStarter.java:128)
    at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:305)
    at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192)
    at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105)
    at org.apache.maven.cli.MavenCli.execute (MavenCli.java:956)
    at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:290)
    at org.apache.maven.cli.MavenCli.main (MavenCli.java:194)
    at sun.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke (NativeMethodAccessorImpl.java:62)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke (DelegatingMethodAccessorImpl.java:43)
    at java.lang.reflect.Method.invoke (Method.java:498)
    at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced (Launcher.java:289)
    at org.codehaus.plexus.classworlds.launcher.Launcher.launch (Launcher.java:229)
    at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode (Launcher.java:415)
    at org.codehaus.plexus.classworlds.launcher.Launcher.main (Launcher.java:356)
Caused by: org.apache.maven.plugin.MojoExecutionException: Build image failed
    at com.google.cloud.tools.jib.maven.BuildImageMojo.execute (BuildImageMojo.java:165)
    at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo (DefaultBuildPluginManager.java:137)
    at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:208)
    at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:154)
    at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:146)
    at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:117)
    at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:81)
    at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build (SingleThreadedBuilder.java:56)
    at org.apache.maven.lifecycle.internal.LifecycleStarter.execute (LifecycleStarter.java:128)
    at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:305)
    at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192)
    at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105)
    at org.apache.maven.cli.MavenCli.execute (MavenCli.java:956)
    at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:290)
    at org.apache.maven.cli.MavenCli.main (MavenCli.java:194)
    at sun.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke (NativeMethodAccessorImpl.java:62)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke (DelegatingMethodAccessorImpl.java:43)
    at java.lang.reflect.Method.invoke (Method.java:498)
    at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced (Launcher.java:289)
    at org.codehaus.plexus.classworlds.launcher.Launcher.launch (Launcher.java:229)
    at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode (Launcher.java:415)
    at org.codehaus.plexus.classworlds.launcher.Launcher.main (Launcher.java:356)
Caused by: com.google.api.client.http.HttpResponseException: 415 Unsupported Media Type
{"errors":[{"code":"MANIFEST_INVALID","detail":{"message":"manifest schema version not supported"},"message":"manifest invalid"}]}

    at com.google.api.client.http.HttpRequest.execute (HttpRequest.java:1070)
    at com.google.cloud.tools.jib.http.Connection.send (Connection.java:130)
    at com.google.cloud.tools.jib.registry.RegistryEndpointCaller.call (RegistryEndpointCaller.java:173)
    at com.google.cloud.tools.jib.registry.RegistryEndpointCaller.call (RegistryEndpointCaller.java:141)
    at com.google.cloud.tools.jib.registry.RegistryClient.callRegistryEndpoint (RegistryClient.java:338)
    at com.google.cloud.tools.jib.registry.RegistryClient.pushManifest (RegistryClient.java:234)
    at com.google.cloud.tools.jib.builder.steps.PushImageStep.afterAllPushed (PushImageStep.java:137)
    at com.google.common.util.concurrent.CombinedFuture$CallableInterruptibleTask.runInterruptibly (CombinedFuture.java:181)
    at com.google.common.util.concurrent.InterruptibleTask.run (InterruptibleTask.java:57)
    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)

Additional Information:

The text was updated successfully, but these errors were encountered:

chanseokoh · 2018-07-24T14:53:53Z

code":"MANIFEST_INVALID",
"detail":{
    "message":"manifest schema version not supported"
},
"message":"manifest invalid"

I am suspecting your Quay only supports schema 1 and not schema 2. Is there a way to configure your registry to also accept schema 2?

Related: #534

chanseokoh · 2018-07-24T15:02:31Z

Seems like Quay still doesn't support schema 2: moby/buildkit#409 (comment)

~~@warmuuh can you try creating and pushing an OCI image? You just put <format>OCI</format> as in the example below:~~
~~https://github.com/GoogleContainerTools/jib/tree/master/jib-maven-plugin#example~~

briandealwis · 2018-07-24T15:40:33Z

There are no such options on Quay.io.

briandealwis · 2018-07-24T15:59:39Z

Odd, but I get a different error when trying to build to quay.io: none of my layer pushes succeed.

Tried to push BLOB for quay.io/briandealwis/foo with digest sha256:8f125ded1b483229a567e48eece98cc8867c2bee55fb73e9cd65ceecc448b7c7 but failed because: unknown: Invalid request | If this is a bug, please file an issue at https://github.com/GoogleContainerTools/jib/issues/new: 400 BAD REQUEST
[ERROR] {"errors":[{"code":"INVALID_REQUEST","detail":{},"message":"Invalid request"}]}

briandealwis · 2018-07-24T17:38:41Z

Ah @warmuuh must be running against Quay Enterprise. My INVALID_REQUEST error above is because we're not fully implementing the Cross Repository Blob Mount request which specifies that the POST request should have both a mount and a from. I'll open a new issue to track that.

Otherwise this is a duplicate of #601. Will retitle slightly. (And unfortunately using OCI doesn't work against quay.io.)

briandealwis · 2018-07-24T17:39:47Z

Duplicate of #601

warmuuh · 2018-07-25T07:37:00Z

yes, i am using quay enterprise. after changing to OCI, i get the same error

 {"errors":[{"code":"MANIFEST_INVALID","detail":{"message":"manifest schema version not supported"},"message":"manifest invalid"}]}

please close, if this is a duplicate

coollog · 2018-08-08T15:15:03Z

Closing in favor of #601

chanseokoh mentioned this issue Jul 24, 2018

Jib build fails to older versions of docker-registry #701

Closed

briandealwis marked this as a duplicate of #601 Jul 24, 2018

briandealwis mentioned this issue Jul 24, 2018

Blob Pusher missing required from parameter #703

Closed

chanseokoh mentioned this issue Jul 24, 2018

Check using Quay as the registry. #500

Closed

coollog added this to the v0.9.9 milestone Jul 25, 2018

coollog closed this as completed Aug 8, 2018

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

pushing to Quay fails #698

pushing to Quay fails #698

warmuuh commented Jul 24, 2018 •

edited

Loading

chanseokoh commented Jul 24, 2018

chanseokoh commented Jul 24, 2018 •

edited

Loading

briandealwis commented Jul 24, 2018

briandealwis commented Jul 24, 2018

briandealwis commented Jul 24, 2018 •

edited

Loading

briandealwis commented Jul 24, 2018

warmuuh commented Jul 25, 2018 •

edited

Loading

coollog commented Aug 8, 2018

pushing to Quay fails #698

pushing to Quay fails #698

Comments

warmuuh commented Jul 24, 2018 • edited Loading

chanseokoh commented Jul 24, 2018

chanseokoh commented Jul 24, 2018 • edited Loading

briandealwis commented Jul 24, 2018

briandealwis commented Jul 24, 2018

briandealwis commented Jul 24, 2018 • edited Loading

briandealwis commented Jul 24, 2018

warmuuh commented Jul 25, 2018 • edited Loading

coollog commented Aug 8, 2018

warmuuh commented Jul 24, 2018 •

edited

Loading

chanseokoh commented Jul 24, 2018 •

edited

Loading

briandealwis commented Jul 24, 2018 •

edited

Loading

warmuuh commented Jul 25, 2018 •

edited

Loading