Repository navigation
Option --http-relative-path not available in prod mode #10567
Replies: 3 comments 3 replies
|
It's a build option, so you'll have to use it in this step (https://www.keycloak.org/server/all-config?f=build). or |
|
ah right, I used it in start-dev mode as an cmd line option and it worked, so was confused a bit. Indeed it works the way you describe and also when added into Dockerfile and re-building the image. |
|
were you able to start it in production mode |
|
This is my docker file FROM quay.io/keycloak/keycloak:17.0.0 But still this path is not added |
|
@sreekesh93 have you tried to set it as as ENV vars in Docker file and then build it? ENV KC_METRICS_ENABLED=true RUN /opt/keycloak/bin/kc.sh build I followed this guide: https://www.keycloak.org/server/containers |
|
+1 on 20.0.2 |
Uh oh!
There was an error while loading. Please reload this page.
Hi,
migration guide states the removal of /auth from context path and that it could be set if need be for compatibility via the option
--http-relative-path. However it looks like this is only available in dev mode, in prod mode getting this error during startup:not sure if this is a bug or how else to run this with this "/auth" context path.
Any hints much appreciated.
All reactions