-
Bug
-
Resolution: Done
-
Major
-
1.5.0.Beta1
-
None
-
False
-
False
-
Undefined
-
-
When starting the docker image (debezium/server:1.5) as a container, you get a stack trace (see below).
Looking a bit further into the build, I noticed that the quarkus version has been updated, with a different default application packaging type as a consequence (which doesn't produce a -runner.jar anymore), see https://github.com/quarkusio/quarkus/wiki/Migration-Guide-1.12#fast-jar-as-default
ls: cannot access 'debezium-server-*runner.jar': No such file or directoryls: cannot access 'debezium-server-*runner.jar': No such file or directoryException in thread "main" java.lang.RuntimeException: java.lang.reflect.InvocationTargetException at io.quarkus.launcher.QuarkusLauncher.launch(QuarkusLauncher.java:58) at io.quarkus.runtime.Quarkus.launchFromIDE(Quarkus.java:96) at io.quarkus.runtime.Quarkus.run(Quarkus.java:83) at io.quarkus.runtime.Quarkus.run(Quarkus.java:42) at io.quarkus.runtime.Quarkus.run(Quarkus.java:119) at io.debezium.server.Main.main(Main.java:15)Caused by: java.lang.reflect.InvocationTargetException at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.base/java.lang.reflect.Method.invoke(Method.java:566) at io.quarkus.launcher.QuarkusLauncher.launch(QuarkusLauncher.java:56) ... 5 moreCaused by: java.lang.RuntimeException: io.quarkus.bootstrap.resolver.maven.BootstrapMavenException: Failed to locate project pom.xml for /debezium/lib/debezium-server-core-1.5.0.Beta1.jar at io.quarkus.bootstrap.IDELauncherImpl.launch(IDELauncherImpl.java:80) ... 10 moreCaused by: io.quarkus.bootstrap.resolver.maven.BootstrapMavenException: Failed to locate project pom.xml for /debezium/lib/debezium-server-core-1.5.0.Beta1.jar at io.quarkus.bootstrap.resolver.maven.workspace.LocalProject.locateCurrentProjectPom(LocalProject.java:250) at io.quarkus.bootstrap.resolver.maven.workspace.LocalProject.access$000(LocalProject.java:25) at io.quarkus.bootstrap.resolver.maven.workspace.LocalProject$WorkspaceLoader.<init>(LocalProject.java:44) at io.quarkus.bootstrap.resolver.maven.workspace.LocalProject$WorkspaceLoader.<init>(LocalProject.java:33) at io.quarkus.bootstrap.resolver.maven.workspace.LocalProject.loadWorkspace(LocalProject.java:198) at io.quarkus.bootstrap.resolver.maven.workspace.LocalProject.loadWorkspace(LocalProject.java:193) at io.quarkus.bootstrap.IDELauncherImpl.launch(IDELauncherImpl.java:62) ... 10 more
[DBZ-3217] Docker image debezium/server:1.5 won't start
Gunnar Morling
added a comment - Ok, so let's adjust the build then to produce the earlier format again then.
Gunnar Morling
added a comment - Ok, so let's adjust the build then to produce the earlier format again then. 
Jiri Pechanec
added a comment - gunnar.morling I am not sure about the move, I am afraid we are losing two functions we have available right now
- The current assembly removes unnecessary files like connect-file.jar and others
- We allow the user to configure application.properties in the conf directory. I have strong feeling this is not possible with the fast-jar
Jiri Pechanec
added a comment - gunnar.morling I am not sure about the move, I am afraid we are losing two functions we have available right now
The current assembly removes unnecessary files like connect-file.jar and others
We allow the user to configure application.properties in the conf directory. I have strong feeling this is not possible with the fast-jar
Gunnar Morling
added a comment - Yes, let's move to fast JAR; it's the default in Quarkus by now and I'm trusting the Quarkus folks that it is stable.
Gunnar Morling
added a comment - Yes, let's move to fast JAR; it's the default in Quarkus by now and I'm trusting the Quarkus folks that it is stable. Jiri Pechanec
added a comment - gunnar.morling Do we prefer to switch to fast jar or just configure the quarkus to generate the previous format?
Jiri Pechanec
added a comment - gunnar.morling Do we prefer to switch to fast jar or just configure the quarkus to generate the previous format? 
Ryan Dunckel (Inactive)
added a comment - I got the same issue, it looks like the -runner.jar isn't being packaged in the dist archive (but it is there in 1.5.0-Alpha1)
Ryan Dunckel (Inactive)
added a comment - I got the same issue, it looks like the -runner.jar isn't being packaged in the dist archive (but it is there in 1.5.0-Alpha1) 
Released