Open bastianhilton opened 8 months ago
Hey @bastianhilton It's a bug in the latest version from keycloak source, more about that here: https://github.com/keycloak/keycloak/issues/25010#issuecomment-1849012822
Workaround, use a previous tag instead of latest, eg: quay.io/keycloak/keycloak:22.0
We are still waiting for the new release to republish as well asap
ok thank you will try that now
same thing happening on elestio/keycloak:22.0.0, should i switch to the keycloak/keycloak:22.0 image or are they the same thing?
You can check our docker-compose file here: https://github.com/elestio-examples/keycloak/blob/main/docker-compose.yaml
When attempting to start keycloak in docker using elestio image, i'm getting this issue:
Use this command-line tool to manage your Keycloak cluster. Options: -cf, --config-file
Set the path to a configuration file. By default, configuration properties are
read from the "keycloak.conf" file in the "conf" directory.
-h, --help This help message.
-v, --verbose Print out error details when running this command.
-V, --version Show version information
:
build Creates a new and optimized server image.
start Start the server.
start-dev Start the server in development mode.
export Export data from realms to a file or directory.
import Import data from a directory or a file.
show-config Print out the current configuration.
tools Utilities for use and interaction with the server.
completion Generate bash/zsh completion script for kc.sh.
:
Start the server in development mode for local development or testing:
$ kc.sh start-dev
Building an optimized server runtime:
$ kc.sh build
Start the server in production mode:
$ kc.sh start
Enable auto-completion to bash/zsh:
$ source <(kc.sh tools completion)
Please, take a look at the documentation for more details before deploying in
production.
Use "kc.sh start --help" for the available options when starting the server.
Use "kc.sh --help" for more information about other commands.
I've added environment variables from here https://hub.docker.com/r/elestio/keycloak and confirmed connection to database via other applications to the same database.
Anything i'm missing, this issue is also with the bitnami/keycloak and regular keycloak docker images as well.