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

apicurio/apicurio-registry-sql image in docker hub seems to be broken #1300

Closed
ChloePont opened this issue Mar 4, 2021 · 4 comments
Closed

Comments

@ChloePont
Copy link

I tried running the latest-snapshot and got the following error:

exec java -Dquarkus.http.host=0.0.0.0 -Djava.util.logging.manager=org.jboss.logmanager.LogManager -javaagent:/opt/agent-bond/agent-bond.jar=jmx_exporter{{9779:/opt/agent-bond/jmx_exporter_config.yml}} -XX:+UseParallelGC -XX:GCTimeRatio=4 -XX:AdaptiveSizePolicyWeight=90 -XX:MinHeapFreeRatio=20 -XX:MaxHeapFreeRatio=40 -XX:+ExitOnOutOfMemoryError -cp . -jar /deployments/apicurio-registry-storage-sql-2.0.0-SNAPSHOT-runner.jar

Exception in thread "main" java.lang.UnsupportedClassVersionError: io/apicurio/registry/services/RegistryConfigSource has been compiled by a more recent version of the Java Runtime (class file version 55.0), this version of the Java Runtime only recognizes class file versions up to 52.0
@jsenko
Copy link
Member

jsenko commented Mar 4, 2021

Hi, we are aware of the problem and updating our Docker files to use JDK 11. @famartinrh correct?

@famarting
Copy link
Contributor

yes exactly, we just fixed that today, there should be a working image published as of today

@ChloePont
Copy link
Author

Nice - thanks for letting me know!
And I assume you're aware but just in case: the build to upgrade to jdk 11 failed earlier today.

@famarting
Copy link
Contributor

yes yes I'm aware, we are working on the fix now

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

No branches or pull requests

3 participants