[bitnami/keycloak] It says "It works!", but not actually works as expected.

[imchaitu]

Name and Version

latest

What architecture are you using?

None

What steps will reproduce the bug?

Just run the yaml example given in the docker hub page.

What is the expected behavior?

1. When I run the compose file, and access localhost:80, it says " It works! ". Really?? Is this keycloak UI? Did you mention any base url to access? Atlease is it written in logs?
2. Image should be self-complete. When I run the official image, it runs, and I am able to access the UI. But this image needs db and it is not mentioned as prerequisite.
3. Even to configure db (postgresql), it is so complicated, that we have to do so many customizations to the DB container as-well as keycloak container.
4. Please keep it simple to get started.

What do you see instead?

1. Atleast give the base URL which takes me to the keycloak UI.
2. Try to keep it simple, atleast for dev env.
3. Should work fine with official postgresql image with fewer configurations.

Additional information

No response

[migruiz4]

Hi @imchaitu,

Could you please provide more details? What docker-compose did you use?

We do provide an example docker-compose in this repository that can be used as base for a development deployment:
https://github.com/bitnami/containers/blob/main/bitnami/keycloak/docker-compose.yml

I deployed it and wasn't able to reproduce your issue, and Keycloak UI is available at localhost.

As a side note, I would like to mention that the docker-composes are community-maintained and they are not recommended for production use, as mentioned in the README: https://github.com/bitnami/containers/tree/main/bitnami/keycloak#using-docker-composeyaml

I recommend using our keycloak Helm chart instead of the docker-compose, you will have a ready-to-use deployment quick and easy, and you could use that as a starting point to move from a development environment to a production-ready environment.

To Install the Helm chart you only need a Kubernetes environment of your choice and run the command:

helm install my-release oci://registry-1.docker.io/bitnamicharts/keycloak

That command will deploy for you the latest version of the chart with default settings, and you can find further information about how to further customize your deployment in the README and the values.yaml.

[imchaitu]

Please see the screenshots: 1. The output of 'docker ps'  2. The browser when hit 'localhost'  I expect it to display keycloak UI. If the path is different from 'localhost' it should be mentioned somewhere, no?

…

On Wed, Jan 29, 2025 at 9:06 AM Miguel Ruiz ***@***.***> wrote: Hi @imchaitu <https://github.com/imchaitu>, Could you please provide more details? What docker-compose did you use? We do provide an example docker-compose in this repository that can be used as base for a development deployment: https://github.com/bitnami/containers/blob/main/bitnami/keycloak/docker-compose.yml I deployed it and wasn't able to reproduce your issue, and Keycloak UI is available at localhost. As a side note, I would like to mention that the docker-composes are community-maintained and they are not recommended for production use, as mentioned in the README: https://github.com/bitnami/containers/tree/main/bitnami/keycloak#using-docker-composeyaml I recommend using our keycloak Helm chart instead of the docker-compose, you will have a ready-to-use deployment quick and easy, and you could use that as a starting point to move from a development environment to a production-ready environment. To Install the Helm chart you only need a Kubernetes environment of your choice and run the command: helm install my-release oci://registry-1.docker.io/bitnamicharts/keycloak That command will deploy for you the latest version of the chart with default settings, and you can find further information about how to further customize your deployment in the README <https://github.com/bitnami/charts/blob/main/bitnami/keycloak/README.md> and the values.yaml <https://github.com/bitnami/charts/blob/main/bitnami/keycloak/values.yaml> . — Reply to this email directly, view it on GitHub <#76684 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AEKPCMQX2KGTUCFCROTF6ZD2NCDYDAVCNFSM6AAAAABV5Y4QAWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMMRQHE2DANRTHE> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[migruiz4]

Hi @imchaitu,

I'm sorry but I'm unable to reproduce your issue.

I would say the "It works!" page corresponds to the default page from an apache webserverm but the bitnami/keycloak image does not use Apache webserver, so I think it that page is coming from connecting to a different service.

I suspect you may have the port localhost:80 occupied by another service (an Apache webserver, maybe not deployed with docker) and that is the reason why you are seeing that instead of the Keycloak UI.

Please try using a different port in your Keycloak docker compose (81:8080) and give it a try at http://localhost:81

Additionally, you can see what process is actually using the port 80 using the commands lsof or netstat. E.g lsof -P -iTCP -sTCP:LISTEN.

[imchaitu]

Hello @migruiz4 ,
I feel very silly!
Yes, you are correct! I have an apache servie running on port 80.
The reason why I overlooked is, in the past, when I try to use the port in docker compose which is already under use, I used to get an error saying that the port is already blocked. I did get any of that, so I thought this is what running on 80.
Howerever, this might be the special case with the wsl setup on windows. Apache service was running as windows servce and I was running docker in WSL (ubunt).

Anyway, thank you for taking the issue seriously.
I am very sorry to waste your time with my sillyness.