Camunda 8 Self Managed docker compose keycloak not start

Camunda 8 Topics Discussion & Questions
8

Hi @Hafflgav

I managed to start the keycloak container inspired by this post: DB_ADDR unbound variable error - #13 by lmsurpre - Configuring the server - Keycloak

So, I added DB_VENDOR=h2 to keycloak parameters:

  keycloak: # https://hub.docker.com/r/jboss/keycloak
    container_name: keycloak
    image: jboss/keycloak:${KEYCLOAK_VERSION:-16.1.1}
    ports:
      - "18080:8080"
    environment:
      DB_VENDOR: h2
      KEYCLOAK_USER: admin
      KEYCLOAK_PASSWORD: admin
    volumes:
      - "./.keycloak/themes/identity:/opt/jboss/keycloak/themes/identity"
    networks:
      - identity-network

But, now Optimize container didn’t start :frowning:
It says:

*Starting Camunda Optimize 3.8.2...*

*15:38:08.026 [main] INFO  o.c.o.s.e.OptimizeElasticsearchClientFactory - Initializing Elasticsearch rest client...*
*15:38:13.735 [main] ERROR o.c.o.s.e.OptimizeElasticsearchClientFactory - Can't connect to any Elasticsearch node [[host=http://elasticsearch:9200]]. Please check the connection!*
*org.elasticsearch.ElasticsearchException: java.util.concurrent.ExecutionException: java.net.ConnectException: Connection refused*

Elasticsearch container works. A GET on http://localhost:9200 return:

{
  "name" : "41227efc0e91",
  "cluster_name" : "docker-cluster",
  "cluster_uuid" : "8lVzr8rgSQOjxmCkaj3_0g",
  "version" : {
    "number" : "7.17.0",
    "build_flavor" : "default",
    "build_type" : "docker",
    "build_hash" : "bee86328705acaa9a6daede7140defd4d9ec56bd",
    "build_date" : "2022-01-28T08:36:04.875279988Z",
    "build_snapshot" : false,
    "lucene_version" : "8.11.1",
    "minimum_wire_compatibility_version" : "6.8.0",
    "minimum_index_compatibility_version" : "6.0.0-beta1"
  },
  "tagline" : "You Know, for Search"
}
1 Like