You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I deployed Keycloak on an ARM64 host with Kubernetes, using Oracle DB as the database.
I had been successfully using version 24 without any issues. However, after updating to version 25, the following error occurred:
io.quarkus.runtime.configuration.ConfigurationException: Unable to find the JDBC driver (oracle.jdbc.driver.OracleDriver)
I suspected this might be an issue specific to version 25, so I tested it with version 26.1.0 as well. Unfortunately, the same error occurred.
When I downgraded the image back to version 24.0.2, everything worked as expected.
Below are the environment variables I used to deploy Keycloak on Kubernetes:
I expect to be able to upgrade Keycloak seamlessly from version 24 to version 25 and eventually to version 26 without any issues.
What do you see instead?
I encountered the following error:
ERROR: io.quarkus.builder.BuildException: Build failure: Build failed due to errors
[error]: Build step org.keycloak.quarkus.deployment.KeycloakProcessor#checkJdbcDriver threw an exception: io.quarkus.runtime.configuration.ConfigurationException: Unable to find the JDBC driver (oracle.jdbc.driver.OracleDriver). You need to install it.
at org.keycloak.quarkus.deployment.KeycloakProcessor.throwConfigError(KeycloakProcessor.java:327)
at org.keycloak.quarkus.deployment.KeycloakProcessor.checkJdbcDriver(KeycloakProcessor.java:299)
at java.base/java.lang.invoke.MethodHandle.invokeWithArguments(MethodHandle.java:733)
at io.quarkus.deployment.ExtensionLoader$3.execute(ExtensionLoader.java:856)
at io.quarkus.builder.BuildContext.run(BuildContext.java:256)
at org.jboss.threads.ContextHandler$1.runWith(ContextHandler.java:18)
at org.jboss.threads.EnhancedQueueExecutor$Task.doRunWith(EnhancedQueueExecutor.java:2516)
at org.jboss.threads.EnhancedQueueExecutor$Task.run(EnhancedQueueExecutor.java:2495)
at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1521)
at java.base/java.lang.Thread.run(Thread.java:1583)
at org.jboss.threads.JBossThread.run(JBossThread.java:483)
ERROR: Unable to find the JDBC driver (oracle.jdbc.driver.OracleDriver). You need to install it.
For more details, run the same command passing the '--verbose' option. Also, you can use '--help' to see the details about the usage of the particular command.
Additional information
No response
The text was updated successfully, but these errors were encountered:
konempty
changed the title
Container does not start - Unable to find the JDBC driver (oracle.jdbc.driver.OracleDriver)
[bitnami/keycloak] Container does not start - Unable to find the JDBC driver (oracle.jdbc.driver.OracleDriver)
Jan 26, 2025
It seems that newer versions of Keycloak removed the Oracle driver for licensing issues. keycloak/keycloak#29491
The solution would be to externally install the driver (you could use initContainers, extraVolumes and extraVolumeMounts for that). However, I would ask the keycloak devs for the proper solution.
Name and Version
bitnami/keycloak:26.1.0
What architecture are you using?
arm64
What steps will reproduce the bug?
I deployed Keycloak on an ARM64 host with Kubernetes, using Oracle DB as the database.
I had been successfully using version 24 without any issues. However, after updating to version 25, the following error occurred:
I suspected this might be an issue specific to version 25, so I tested it with version 26.1.0 as well. Unfortunately, the same error occurred.
When I downgraded the image back to version 24.0.2, everything worked as expected.
Below are the environment variables I used to deploy Keycloak on Kubernetes:
What is the expected behavior?
I expect to be able to upgrade Keycloak seamlessly from version 24 to version 25 and eventually to version 26 without any issues.
What do you see instead?
I encountered the following error:
Additional information
No response
The text was updated successfully, but these errors were encountered: