Skip to content

Replace deprecated Bitnami Kafka image to ensure Makefiles and scripts keep working #16

@igor-soldev

Description

@igor-soldev

Hi,

I noticed that the local development setup (Docker Compose, Makefiles, and helper scripts) relies on bitnami/kafka:2.

The Problem

  1. Access Restrictions: Bitnami has restricted public access to their images, which can lead to pull access denied errors for contributors.
  2. Hardcoded Paths: Your Makefile and scripts/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.yml
  • cmd/ziggurat/templates/docker-compose.yml.tpl
  • (Indirectly benefits Makefile and scripts/* by keeping them valid)

I can submit a PR to update the image reference. Would you be open to that?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions