kafdrop: Kafdrop 4.0.0 Docker image doesn't start

Well, this is the Docker image, we are not modifying it anyhow. We are not using it as a base image for our image; it’s used “as is”. So there are no our libraries involved. I believe Kotlin is used indirectly as a dependency of some module in your project; most probably - its somehow related to SpringBoot. But it’s definitely exists there: please check the screenshot of contents of obsidiandynamics/kafdrop:latest Docker image I made in Docker Desktop:

On the right side, I filtered used packages by the ‘kotlin’ keyword. You can see there are some of them. The previous (working) version, 3.31.0, also contains them, but the lower versions, of course:

More of that: I tried to run docker-compose.yaml your project has in docker-compose/kafka-kafdrop folder with exactly the same result: the kafka container was started successfully, while the kafdrop failed with exactly the same error. I’m not saying the error is somewhere in the Kafdrop code. It could be that it’s somewhere in the base image Kafdrop using for the own image: eclipse-temurin:17.0.8.1_1-jdk. Or it’s something related to the way how the image prepared on your side; we experienced a similar problem in the past in our building environment.

Yes @mehdihasan, I can confirm, that with the -Xss360K settings Kafdrop4 image starts w/o problems. Thank you! I did test it on my local system so far.

Upd: On the remote systems it started to work as well. Thanks again!

Sorry for not being explicit.

I started with a working situation, then made this change:

-      JVM_OPTS: "-Xms16M -Xmx48M -XX:-TieredCompilation -XX:+UseStringDeduplication -noverify"
+      JVM_OPTS: "-Xms16M -Xmx48M -Xss360K -XX:-TieredCompilation -XX:+UseStringDeduplication -noverify"

That also worked.

I’m also seeing this issue.

Hi @mehdihasan, thank you for the efforts, first of all!

Regarding the used configuration, etc.: Actually, there are nothing special. Our solution’s services are represented as the Docker images and runs in the Docker Swarm mode. Each Swarm has few physical hosts. At the moment, hosts are running under CentOS 7.9.2009, the Docker daemon version is 20.10.5. The compose.yml, which is responsible for the solution’s configuration prepared with Compose V3.7. The Swarm starts with the command: docker stack deploy --with-registry-auth -c compose.yml <swarm_name> The specifically Kafdrop service configured almost in the same way, as in your own compose file: docker-compose/kafka-kafdrop/docker-compose.yaml. Service has got only 1 instance and here its config:

  kafdrop:
    image: obsidiandynamics/kafdrop:latest
    networks:
      - confluent_network
    environment:
      - KAFKA_BROKERCONNECT=confluent-kafka1:9092,confluent-kafka2:19092,confluent-kafka3:29092
      - JVM_OPTS=-Xms16M -Xmx48M -Xss180K -XX:-TieredCompilation -XX:+UseStringDeduplication -noverify
      - SERVER_SERVLET_CONTEXTPATH=/kafdrop
    depends_on:
      - confluent-kafka1
      - confluent-kafka2
      - confluent-kafka3
    deploy:
      restart_policy:
        condition: on-failure

As I already mentioned above, we are using your image “as is”, so, in general, it should contain everything for the correct work and other services aren’t really able to influence the used libraries/dependencies within Kafdrop container. However, when the error occurs, I tried to start your docker compose file on my local box. My box is running under the macOS Monterey (12.6.4), for Docker related stuff I’m using Docker Desktop v.4.22.0 (117440). Your compose was started with the following command: docker-compose -f docker-compose.yaml -p obsidiandynamics up When you’ve requested for a log, I just run your compose file one more time and copied the log from kafdrop service; that’s why it was so quick 😉.

p.s. It looks like we are three, who experienced the same problem; at least I considering the thumb emoji from the @moein7 user like that 😉.

I just got the same Error while trying to start the image. Downgraded to 3.31.0 - and no issues with it.