OK thank you, this was exactly the problem. My previous questions are rendered obsolete by this answer. All works now as expected. Best regards, Lukasz Lech From: Sebastian Laskawiec [mailto:slaskawi@redhat.com] Sent: Mittwoch, 10. Oktober 2018 14:04 To: Lukasz Lech <l.lech(a)ringler.ch&gt; Cc: keycloak-dev(a)lists.jboss.org Subject: Re: [keycloak-dev] Confusion about standalone.xml in docker image jboss/keycloak.4.5.0.Final We've changed the default configuration to standalone-ha.xml recently. Try modifying that one. On Wed, Oct 10, 2018 at 1:45 PM Lukasz Lech <l.lech@ringler.ch<mailto:l.lech@ringler.ch>> wrote: Hello, I'm finally confused about docker image jboss/keycloak.4.5.0.Final and config files there. I've applied changes to /opt/jboss/keycloak/standalone/configuration/standalone.xml but they've take no effect. I've checked that server starts in standalone mode, positive. After many tries I've made a mad step, deleting that configuration file (in my Dockerfile, not in running container!). To my full surprise the keycloak started without any warning. What is the purpose of that configuration file, then? If that file is not used, what configuration file is used? I can delete standalone_ha.xml as well as the whole /opt/jboss/keycloak/domain/configuration, it doesn't disturb the server in any way. Best regards, Lukasz Lech _______________________________________________ keycloak-dev mailing list keycloak-dev@lists.jboss.org<mailto:keycloak-dev@lists.jboss.org> https://lists.jboss.org/mailman/listinfo/keycloak-dev