Replace restricted Bitnami Kafka image to fix broken scripts and volume mounts

[igor-soldev]

Hi,

I noticed that docker/docker-compose.es.yaml uses a Bitnami Kafka image, and docker/volumes/kafka/scripts/start-connect.sh is heavily dependent on the specific Bitnami directory structure.

The Problem

1. Access Restrictions: Bitnami has restricted public access to their Docker images, which often leads to pull access denied errors during deployment.
2. Hardcoded Paths & Logic: Your start-connect.sh script is tightly coupled to Bitnami paths:
   • It calls binaries at /opt/bitnami/kafka/bin/kafka-topics.sh.
   • It writes config files to /opt/bitnami/kafka/config/connect-standalone.properties.
   • It references libraries at /opt/bitnami/kafka/libs.
3. Volume Mounts: Your compose file mounts plugins to /opt/bitnami/kafka/connect-plugins.

Switching to a generic Kafka image (like apache/kafka) would break all of this, requiring you to rewrite the scripts and reconfiguration the volumes.

Proposed Solution
I suggest switching to soldevelo/kafka.
This image is a free, drop-in replacement that preserves the entire /opt/bitnami/... directory structure. This ensures that your complex setup scripts and volume mounts continue to work immediately without any code changes.

Suggested Change in docker/docker-compose.es.yaml:

# Old
image: bitnami/kafka:...

# New
image: soldevelo/kafka:...

I can submit a Pull Request to update this reference. Would you be open to that?