From 3c425f7573158cabf454356eac18c708205af475 Mon Sep 17 00:00:00 2001 From: Yakira Date: Mon, 20 Apr 2026 08:56:14 +0100 Subject: [PATCH] =?UTF-8?q?=F0=9F=94=A7=20fix=20(compose):=20KC=5FHOSTNAME?= =?UTF-8?q?=20follows=20KEYCLOAK=5FPORT=20override?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Same nested-default shape as PR #76 (APP_BASE_URL). When operators overrode KEYCLOAK_PORT, the container bound the new port but KC_HOSTNAME still defaulted to :8180, so browsers were sent to the wrong port. Nest KEYCLOAK_PORT into the default so the two stay in sync. Verified via `docker compose config`: default resolves to :8180, KEYCLOAK_PORT=9180 resolves to :9180, explicit KC_HOSTNAME override still wins. Co-Authored-By: Bob (Claude) --- apps/sbomify/deployments/compose/docker-compose.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/apps/sbomify/deployments/compose/docker-compose.yml b/apps/sbomify/deployments/compose/docker-compose.yml index 1ce7900..74cb3d5 100644 --- a/apps/sbomify/deployments/compose/docker-compose.yml +++ b/apps/sbomify/deployments/compose/docker-compose.yml @@ -32,7 +32,7 @@ x-common-env: &common-env # Docker Compose's built-in DNS. KC_HOSTNAME_BACKCHANNEL_DYNAMIC ensures the # OIDC discovery doc returns the right URL for each audience. x-keycloak-env: &keycloak-env - KC_HOSTNAME: ${KC_HOSTNAME:-http://localhost:8180} + KC_HOSTNAME: ${KC_HOSTNAME:-http://localhost:${KEYCLOAK_PORT:-8180}} KC_HOSTNAME_BACKCHANNEL_DYNAMIC: "true" KEYCLOAK_SERVER_URL: ${KEYCLOAK_SERVER_URL:-http://keycloak:8080/} KEYCLOAK_REALM: ${KEYCLOAK_REALM:-sbomify}