-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
bitnami/ksql:7.8.0-debian-12-r0 #75665
Comments
adding in guava for the com.google.common.collect.ImmutableSet failure then fails with:
this one is present in /opt/bitnami/ksql/share/java/kafka/ the connect-api jar
|
I finally got it to run with the following additional jar files:
I also added the following class path (which is probably overkill):
I note that the run script /opt/bitnami/ksql/bin/ksql-run-class has some logic for adding in exta paths non of which exist in this image
we could in the same way add all the folders under /opt/bitnami/ksql/share/java/
the dockerfile https://github.com/bitnami/containers/blob/main/bitnami/ksql/7.8/debian-12/Dockerfile |
I think log4j 1.2 should really be removed as logging is two of the issues here it might be worth including that requires removing:
and then I add the following (for completeness):
it also needs the log4j.properties replacing with a log4j2 file |
I would look at adding a PR if someone could point me to the thing that creates the tar file |
OK I've looked again and it seems the only thing needed is the classpath fix
the folder /opt/bitnami/ksql/share/java/acl contains a shaded jar with all the dependencies but the startup sequence of scripts aren't including it it's a shame it's all in one jar as I really don't want to use log4j 1.2 but that's another issue |
Name and Version
bitnami/ksql:7.8.0-debian-12-r0
What architecture are you using?
amd64
What steps will reproduce the bug?
I also have a docker compose file that I'm using to test but the missing jar files seem to be causing the failure and this is the simplest example
What is the expected behavior?
problem connecting to broker
What do you see instead?
a stack trace:
Additional information
adding in the slf4j-api-2.0.9.jar then subsequently fails with:
The text was updated successfully, but these errors were encountered: