Skip to content

Update restricted Bitnami Kafka image to ensure volume mounts work #247

@igor-soldev

Description

@igor-soldev

Hi,

I noticed that docker/infra-compose.yml relies on a bitnami/kafka image and explicitly mounts a volume to /bitnami/kafka.

The Problem
Bitnami has restricted public access to their Docker images, which often leads to pull access denied errors for developers trying to spin up this environment.
Crucially, your configuration uses:
- kafka-data:/bitnami/kafka

Switching to a generic Kafka image (like apache/kafka) would break this persistence because standard images do not use the /bitnami directory structure.

Proposed Solution
I suggest switching to soldevelo/kafka.
This image is a free, drop-in replacement that preserves the /bitnami/kafka directory structure. This ensures your volume mounts and existing data persistence logic continue to work exactly as they do now, but without the registry restrictions.

Suggested Change in docker/infra-compose.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?

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