Skip to content

Replace restricted Bitnami Kafka images to fix Ansible pulls and Docker Compose setups #25

@igor-soldev

Description

@igor-soldev

Hi team,

I noticed that your tools/docker-kafka setups and the cloudlab-ansible/docker_images.yml playbook rely on bitnami/kafka:3.5.

The Problem
Bitnami has restricted public access to their Docker images.

  1. Ansible Failure: The command docker pull bitnami/kafka:3.5 in cloudlab-ansible/docker_images.yml will likely fail with an "access denied" error when running on new cloud nodes, breaking the automated deployment.
  2. Compose Failure: Users trying to spin up the Kafka clusters using the docker-compose-kafka*.yaml files will encounter similar pull errors.

Proposed Solution
I suggest switching to soldevelo/kafka:3.5.
This image is a free, drop-in replacement that works exactly like the Bitnami version (preserving configuration and environment variables), but it allows for unrestricted pulling, ensuring your automation scripts and benchmarks run smoothly.

Suggested Changes:

1. In cloudlab-ansible/docker_images.yml:

# Old
docker pull bitnami/kafka:3.5

# New
docker pull soldevelo/kafka:3.5

2. In tools/docker-kafka/docker-compose*.yaml files:

# Old
image: docker.io/bitnami/kafka:3.5

# New
image: soldevelo/kafka:3.5

Affected files:

  • cloudlab-ansible/docker_images.yml
  • tools/docker-kafka/docker-compose.yaml
  • tools/docker-kafka/docker-compose-kafka1.yaml through kafka4.yaml

I can submit a Pull Request to update these references across the repository. 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