Replace restricted Bitnami Kafka image to ensure scripts and volume mounts work

[igor-soldev]

Hi,

I noticed that docker/docker-compose.enterprise.yml relies on bitnami/kafka and that docker/volumes/kafka/scripts/start-connect.sh contains hardcoded paths to the 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.
2. Hardcoded Script Paths: Your script start-connect.sh executes commands explicitly using:
   /opt/bitnami/kafka/bin/kafka-topics.sh
3. Volume Mounts: Your compose file mounts data to:
   - kafka-data:/bitnami/kafka

Switching to a generic Kafka image (like apache/kafka) would break both the scripts (binary paths would change) and the volume persistence, requiring refactoring.

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

Suggested Change in docker/docker-compose.enterprise.yml:

# Old
image: bitnami/kafka:...

# New
image: soldevelo/kafka:...

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