Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

OCI docker push fails #675

Closed
andriy-dmytruk opened this issue Mar 20, 2023 · 2 comments · Fixed by micronaut-projects/micronaut-core#8980
Closed

OCI docker push fails #675

andriy-dmytruk opened this issue Mar 20, 2023 · 2 comments · Fixed by micronaut-projects/micronaut-core#8980

Comments

@andriy-dmytruk
Copy link
Contributor

andriy-dmytruk commented Mar 20, 2023

Reproduce

As described in the Deploy serverless application to OCI guide:

Error

[ERROR] Failed to execute goal com.google.cloud.tools:jib-maven-plugin:3.1.4:dockerBuild (default-dockerBuild) on project demo: Tried to pull image manifest for registry-1.docker.io/fnproject/fn-java-fdk:latest but failed because: OCI index found, but accept header does not support OCI indexes: 404 Not Found
[ERROR] {"errors":[{"code":"MANIFEST_UNKNOWN","message":"OCI index found, but accept header does not support OCI indexes"}]}
[ERROR] -> [Help 1]
[ERROR] 
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR] 
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException

Full log: log.txt, stacktrace: stacktrace.txt.

Seems like the issue is when pulling fn-java-fdk and some kind of oci accept header is missing in the request. But when I run docker pull fnproject/fn-java-fdk:latest, it works fine.

Not sure if the problem is similar to this one: fraunhoferfokus/deckschrubber#43

@alvarosanchez
Copy link
Member

The error goes away with the latest version of Jib. I've created a PR to bump to that version, but we can only include it in Micronaut 3.9.x.

In the meantime, you can set the property <jib-maven-plugin.version>3.3.1</jib-maven-plugin.version> in your POM.

@andriy-dmytruk
Copy link
Contributor Author

@alvarosanchez This fixes the issue. Thank you

alvarosanchez added a commit to micronaut-projects/micronaut-core that referenced this issue Mar 21, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants