-
Notifications
You must be signed in to change notification settings - Fork 12
Open
Description
Hi,
I noticed that the local development setup (Docker Compose, Makefiles, and helper scripts) relies on bitnami/kafka:2.
The Problem
- Access Restrictions: Bitnami has restricted public access to their images, which can lead to
pull access deniederrors for contributors. - Hardcoded Paths: Your
Makefileandscripts/produce_*files execute commands inside the container using specific paths like:
/opt/bitnami/kafka/bin/kafka-topics.sh
/opt/bitnami/kafka/bin/kafka-console-producer.sh
Switching to a standard image (like apache/kafka) would break these scripts because the binary paths would be different.
Proposed Solution
I suggest switching to soldevelo/kafka:2 (or a newer version if you prefer).
This image is a drop-in replacement that preserves the /opt/bitnami/... directory structure. This means your Makefiles and helper scripts will continue to work immediately without needing to rewrite all the paths.
Suggested Change
Update docker-compose.yml and cmd/ziggurat/templates/docker-compose.yml.tpl:
# Old
image: 'bitnami/kafka:2'
# New
image: 'soldevelo/kafka:2'Affected files:
docker-compose.ymlcmd/ziggurat/templates/docker-compose.yml.tpl- (Indirectly benefits
Makefileandscripts/*by keeping them valid)
I can submit a PR to update the image reference. Would you be open to that?
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels