Closed strainovic closed 2 years ago
Same issue here, since I've upgrade to the latest version of Helm chart (10.1.2).
It looks like the command is based on the chart .AppVersion
, but that the container is missing the correct jar file.
Workaround for now, override the job command. In Helm values:
keycloakConfigCli:
command:
- java
- -jar
- /opt/bitnami/keycloak-config-cli/keycloak-config-cli-19.0.1.jar
Hi @strainovic, this happens because there hasn't been a release of keycloak-config-cli for 19.0.2 yet: https://github.com/adorsys/keycloak-config-cli/releases
If you have any ideas on how to improve the current chart, feel free to contribute with a PR, we'd be glad to help with the review and release if needed.
This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.
Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary.
the bot is wrong
Name and Version
bitnami/keycloak 10.1.2
What steps will reproduce the bug?
Are you using any custom parameters or values?
No
What is the expected behavior?
To run the job successfully.
What do you see instead?
Error: Unable to access jarfile /opt/bitnami/keycloak-config-cli/keycloak-config-cli-19.0.2.jar
Additional information