Camunda 8 Self Managed docker-compose operate and tasklist not starting

Hi,

I am trying to evaluate Camunda 8 Self-Managed using docker-compose configuration on a Ubuntu 22.04.1 with Docker 20.10.21.

4f75742b3218   camunda/connectors-bundle:8.5.2                        "/start.sh"              4 days ago      Up 4 days (unhealthy)   0.0.0.0:8085->8080/tcp, :::8085->8080/tcp                                                                                                              connectors
1e6bae55d8d3   camunda/zeebe:8.5.0                                    "tini -- /usr/local/…"   4 days ago      Up 4 days (healthy)     0.0.0.0:9600->9600/tcp, :::9600->9600/tcp, 0.0.0.0:26500->26500/tcp, :::26500->26500/tcp, 26501-26502/tcp, 0.0.0.0:8088->8080/tcp, :::8088->8080/tcp   zeebe
4ea5c06b16e9   camunda/optimize:8.5.1                                 "/sbin/tini -- ./opt…"   4 days ago      Up 4 days (healthy)     8091/tcp, 0.0.0.0:8083->8090/tcp, :::8083->8090/tcp                                                                                                    optimize
62ce366538d8   camunda/identity:8.5.0                                 "java -jar identity.…"   4 days ago      Up 4 days (healthy)     8080/tcp, 0.0.0.0:8084->8084/tcp, :::8084->8084/tcp                                                                                                    identity
0cedb3edfffc   bitnami/keycloak:21.1.2                                "/opt/bitnami/script…"   4 days ago      Up 4 days (healthy)     0.0.0.0:18080->8080/tcp, :::18080->8080/tcp                                                                                                            keycloak
4949e00884c5   docker.elastic.co/elasticsearch/elasticsearch:8.13.4   "/bin/tini -- /usr/l…"   4 days ago      Up 4 days (healthy)     0.0.0.0:9200->9200/tcp, :::9200->9200/tcp, 0.0.0.0:9300->9300/tcp, :::9300->9300/tcp                                                                   elasticsearch
eaa1b0e9140b   postgres:14.5-alpine                                   "docker-entrypoint.s…"   4 days ago      Up 4 days (healthy)     5432/tcp                                                                                                                                               postgres

connectors unhealthy,Discovered through logs that operator cannot connect.

5f1677c399e3   camunda/tasklist:8.5.0                                 "/sbin/tini -- /usr/…"   4 days ago      Exited (255) 4 days ago
07c866f5c833   camunda/operate:8.5.0                                  "/sbin/tini -- /usr/…"   4 days ago      Exited (255) 34 seconds ago 

operate and tasklist contain the same logs, and the service cannot start

Operate is a tool in Camunda 8 stack to provide visibility into all your processes and resolve any incident from a centralized platform. More information can be found on https://camunda.com/platform/operate/

License
The licensing information for Operate available at: https://docs.camunda.io/docs/reference/licenses/

Login with the credentials:
  User:     demo
  Password: demo

   ___   _   __  __ _   _ _  _ ___   _      ___  ___ ___ ___    _ _____ ___
  / __| /_\ |  \/  | | | | \| |   \ /_\    / _ \| _ \ __| _ \  /_\_   _| __|
 | (__ / _ \| |\/| | |_| | .` | |) / _ \  | (_) |  _/ _||   / / _ \| | | _|
  \___/_/ \_\_|  |_|\___/|_|\_|___/_/ \_\  \___/|_| |___|_|_\/_/ \_\_| |___|

							   8.5.0


2024-05-21 03:08:54.877  INFO 7 --- [kground-preinit] o.h.v.i.u.Version                        : HV000001: Hibernate Validator 8.0.1.Final
2024-05-21 03:08:54.951  INFO 7 --- [           main] i.c.o.Application                        : Starting Application v8.5.0 using Java 17.0.10 with PID 7 (/usr/local/operate/lib/operate-webapp-8.5.0-exec.jar started by camunda in /usr/local/operate)
2024-05-21 03:08:54.958  INFO 7 --- [           main] i.c.o.Application                        : The following 1 profile is active: "identity-auth"
2024-05-21 03:08:57.674  WARN 7 --- [           main] trationDelegate$BeanPostProcessorChecker : Bean 'io.camunda.operate.webapp.security.CustomMethodSecurityExpressionHandler' of type [io.camunda.operate.webapp.security.CustomMethodSecurityExpressionHandler] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying). Is this bean getting eagerly injected into a currently created BeanPostProcessor [healthEndpointGroupsBeanPostProcessor]? Check the corresponding BeanPostProcessor declaration and its dependencies.
2024-05-21 03:08:57.677  WARN 7 --- [           main] trationDelegate$BeanPostProcessorChecker : Bean 'io.camunda.operate.webapp.security.MethodSecurityConfig' of type [io.camunda.operate.webapp.security.MethodSecurityConfig$$SpringCGLIB$$0] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying). Is this bean getting eagerly injected into a currently created BeanPostProcessor [healthEndpointGroupsBeanPostProcessor]? Check the corresponding BeanPostProcessor declaration and its dependencies.
2024-05-21 03:08:58.008  WARN 7 --- [           main] ConfigServletWebServerApplicationContext : Exception encountered during context initialization - cancelling refresh attempt: org.springframework.context.ApplicationContextException: Unable to start web server

How to continue locating the cause of the error.
Can anyone help?
Thanks,

Due to the use of the main branch, the problem was resolved after switching to a confirmed tag. :sweat_smile: