Incorrect Keycloak work when running in a Docker container #45082

smirnoffd · 2025-12-25T09:53:55Z

smirnoffd
Dec 25, 2025

I want to use Keycloak in a Docker container. The first time I run it with the following parameters:
docker-compose.yaml:

services:
  keycloak:
    image: keycloak/keycloak:26.4
    container_name: keycloak
    environment:
      KC_DB: postgres
      KC_DB_URL: jdbc:postgresql://postgres-keycloak:5432/keycloak
      KC_DB_USERNAME: ${POSTGRES_USER}
      KC_DB_PASSWORD: ${POSTGRES_PASSWORD}
      KC_HOSTNAME: https://auth.domain.com
      KC_PROXY_HEADERS: xforwarded
      KC_HOSTNAME_STRICT: true
      KC_HTTP_ENABLED: true
      KC_LOG_LEVEL: info
      KC_METRICS_ENABLED: true
      KC_HEALTH_ENABLED: true
      KEYCLOAK_ADMIN: ${KEYCLOAK_ADMIN}
      KEYCLOAK_ADMIN_PASSWORD: ${KEYCLOAK_ADMIN_PASSWORD}
      JAVA_OPTS_APPEND: "-Xms2g -Xmx4g"
    volumes:
      - /storage/keycloak/themes:/opt/keycloak/themes
      - /storage/keycloak/providers:/opt/keycloak/providers
      - /storage/keycloak/conf:/opt/keycloak/conf
    command: start
    depends_on:
      - postgres-keycloak
    ports:
      - 8080:8080
    networks:
      - keycloak_net

  postgres-keycloak:
    container_name: postgres-keycloak
    image: postgres:18
    ports:
      - "5432:5432"
    volumes:
      - /storage/postgres-keycloak/:/var/lib/postgresql/
    environment:
      POSTGRES_DB: keycloak
      POSTGRES_USER: ${POSTGRES_USER}
      POSTGRES_PASSWORD: ${POSTGRES_PASSWORD}
    networks:
      - keycloak_net

networks:
  keycloak_net:
    driver: bridge

It starts and runs successfully, writes in the logs at the next start to use start --optimized

2025-12-24 18:28:30,997 INFO  [io.quarkus.deployment.QuarkusAugmentor] (main) Quarkus augmentation completed in 10612ms
Server configuration updated and persisted. Run the following command to review the configuration:

	kc.sh show-config

Next time you run the server, just run:

	kc.sh start --optimized

Ok, I run docker compose down, then docker compose up -d in docker-compose.yaml is already changing

command: start

to

command: start --optimized

And an error occurs when starting the container:

ERROR: The '--optimized' flag was used for first ever server start. Please don't use this flag for the first startup or use 'kc.sh build' to build the server first.

If I remove --optimized, then it just starts a new Keycloak instance, but I need it to save all settings and realm to Keycloak even after docker compose down.
Maybe I'm mounting some directories incorrectly?

shawkins · 2025-12-25T17:49:14Z

shawkins
Dec 25, 2025
Collaborator

See https://www.keycloak.org/server/containers for the typical scenario of creating a pre-built image.

0 replies

Navigation Menu

Repository navigation

Incorrect Keycloak work when running in a Docker container #45082

Uh oh!

{{title}}

Uh oh!

Replies: 1 comment

Uh oh!

{{title}}

Uh oh!

Select a reply

Uh oh!

Incorrect Keycloak work when running in a Docker container #45082

Uh oh!

smirnoffd Dec 25, 2025

Replies: 1 comment

Uh oh!

shawkins Dec 25, 2025 Collaborator

smirnoffd
Dec 25, 2025

shawkins
Dec 25, 2025
Collaborator