Repository navigation
Replies: 2 comments 3 replies
|
There's not much information to go by here. The default docker image exposes 8080, 8443, and 9000. If you are changing the http port or do not have http enabled, then 8080 will not be correct. |
|
Thanks for your reply. |
|
You should verify with a docker or podman run that the container is behaving as you expect. If it behaves as expected, then the problem has something to do with how you are configuring it to run in Azure. Also KC_PROXY is no longer used by Keycloak. |
|
Thanks for your response. |
|
Thanks for your response. Error msg: "The TargetPort 8080 does not match any of the listening ports. container crashed" My docker image looks like this.. FROM quay.io/keycloak/keycloak:26.1.4 AS builder ENV KC_HEALTH_ENABLED=true WORKDIR /opt/keycloak RUN /opt/keycloak/bin/kc.sh build FROM quay.io/keycloak/keycloak:26.1.4 ENV KC_HTTP_ENABLED=true ENV KEYCLOAK_ADMIN=admin EXPOSE 8080 ENTRYPOINT ["/opt/keycloak/bin/kc.sh", "start"] Env Variable Set KC_DB=postgresql Set ingress=enabled |
Uh oh!
There was an error while loading. Please reload this page.
Before reporting an issue
Area
No response
Describe the bug
Hello,
I'm trying to deploy quay.io/keycloak/keycloak:26.1.4 image into the Azure container apps. However I get the following issue,
"The TargetPort 8080 does not match any of the listening ports:"
Can someone suggests what the problem on keycloak, i set all required KC_ environment variable. however no luck.
Version
1
Regression
Expected behavior
N/A
Actual behavior
"The TargetPort 8080 does not match any of the listening ports:"
How to Reproduce?
N/A
Anything else?
Please suggest if i;m trying with the right image as this is already setup in VM and works fine. however with container app does not work. Thanks.
All reactions