Let’s use this session to add another realm: docker exec 31a5c280ecdf /opt/jboss/keycloak/bin/kcadm.sh create realms -s realm=wildfly-realm -s enabled=true -o Firstly, we need to login to Keycloak server: docker exec 31a5c280ecdf /opt/jboss/keycloak/bin/kcadm.sh config credentials -server -realm master -user admin -password admin Another option is to use the Keycloak CLI which you can trigger with a docker exec command. One option is using the Web Console as we have seen in the previous section. You can approach Keycloak management on docker in at least two ways. ROOT_LOGLEVEL: Specifies the log level for underlying container (default is INFO)Įxample usage: docker run -rm -name keycloak -e KEYCLOAK_USER=admin -e KEYCLOAK_PASSWORD=admin -p 8180:8180 -it quay.io/keycloak/keycloak:legacy -b 0.0.0.0 -e KEYCLOAK_LOGLEVEL=TRACE Managing Keycloak Realms running on Docker.KEYCLOAK_LOGLEVEL: Specifies the log level for Keycloak (default is INFO).You can set Keycloak log level through the following environment variables:
Then, you will see the following log: Added 'frank' to '/opt/jboss/keycloak/standalone/configuration/keycloak-add-user.json', restart server to load userįinally, restart the container with: docker restart 31a5c280ecdf Changing Keycloak Log Level Next, run the following command: docker exec 31a5c280ecdf /opt/jboss/keycloak/bin/add-user-keycloak.sh -u frank -p foo You can use it to add some extra users.įirstly, collect the container id: $ docker ps The legacy image of Keycloak ships with the script add-user-keycloak script available in the /opt/jboss/keycloak/bin folder. Next, login to the Admin Console, which is available at: with admin/admin: You will see that Keycloak starts in foreground and binds to port 8180 (by default port 8080 will be used but it can clash with other services, like WildFly, running on that port): 09:16:07,923 INFO (Controller Boot Thread) WFLYSRV0025: Keycloak 15.0.2 (WildFly Core 15.0.1.Final) started in 22594ms - Started 692 of 977 services (686 services are lazy, passive or on-demand)Ġ9:16:07,925 INFO (Controller Boot Thread) WFLYSRV0060: Http management interface listening on Ġ9:16:07,925 INFO (Controller Boot Thread) WFLYSRV0051: Admin console listening on To use a different port, such as port 8180, you can use the following command: docker run -rm -name keycloak -e KEYCLOAK_USER=admin -e KEYCLOAK_PASSWORD=admin -p 8180:8180 -it quay.io/keycloak/keycloak:legacy -b 0.0.0.0 =8180
DOCKER RUN IMAGE RESTART HOW TO
Here is how to start it, adding an Admin user: docker run -rm -name keycloak -e KEYCLOAK_USER=admin -e KEYCLOAK_PASSWORD=admin -p 8080:8080 -it quay.io/keycloak/keycloak:legacy Please notice the legacy tag that indicates to use the WildFly distribution. To run the legacy distribution, which uses WildFly as runtime engine, you need to refer to the quay.io/keycloak/keycloak:legacy Image.
DOCKER RUN IMAGE RESTART UPDATE
Update the Database and Keystore settings accordingly. https-key-store-file=server.keystore -https-key-store-password=secret db-url=jdbc:postgresql://localhost:5432/keycloak -db-username=postgres -db-password=postgres \ If you want to start Keycloak on a different server port: docker run -name keycloak_dev -p 8180:8180 \įinally, to start Keycloak in production mode with PostgreSQL as database, use the following example command: docker run -name keycloak_auto_build -p 8080:8080 \ e KEYCLOAK_ADMIN=admin -e KEYCLOAK_ADMIN_PASSWORD=admin \ Here is how to start it in development mode: docker run -name keycloak_dev -p 8080:8080 \ On the other hand, you can pull and start Keycloak with a single command. To pull the latest Docker Image of Keycloak you can run from the Command Line: $ docker pull quay.io/keycloak/keycloak:latest Keycloak with Docker powered by Quarkusįirstly, it is worth mentioning that you can use either the docker command or podman to achieve the same results. That being said, let’s see how to start Keycloak on Docker in both distributions. This distribution will not receive further updates so it’s now a legacy distribution
0 kommentar(er)
