1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.
  2. Anuncie Aqui
    Anuncie aqui você Também: fdantas@4each.com.br

[JBoss] Which Docker registry should be used for Keycloak?

Discussão em 'StackOverflow' iniciado por Stack, Janeiro 20, 2025.

  1. Stack

    Stack Membro Participativo

    Running from a docker compose file

    keycloak:
    image: jboss/keycloak
    container_name: keycloak
    restart: always
    environment:
    KEYCLOAK_USER: admin
    KEYCLOAK_PASSWORD: admin
    ports:
    - "8080:8080"


    Works for me, where "works" means: if I create a realm called wibble (redirect urls *) and a user called user1, when I go to http://localhost:8080/auth/realms/wibble/account I get a login prompt.

    On doing the same thing for quay.io, the same url gives a "We are sorry, page not found" response

    keycloak:
    image: quay.io/keycloak/keycloak:latest
    command: start-dev
    restart: always
    environment:
    KEYCLOAK_ADMIN: admin
    KEYCLOAK_ADMIN_PASSWORD: admin
    ports:
    - 8080:8080


    Also, using the keycloak image from quay.io, http://localhost:8080/ redirects to http://localhost:8080/auth/ which also give the same "We are sorry, page not found" response but going to http://localhost:8080/admin gives a login prompt.

    Am I right in thinking that the quay.io image is the more recent and supported one? And if so, does anyone have any ideas what on earth is going on with that simple docker compose file?

    Continue reading...

Compartilhe esta Página