Hi,
I noticed that the configuration example in README-google-microservices.md uses bitnami/kafka:3.7 and specifically mounts a volume to /bitnami/kafka.
The Problem
Bitnami has restricted public access to their Docker images. Users trying to run this standalone example will likely encounter pull access denied errors.
Crucially, the configuration uses:
- kafka_data:/bitnami/kafka
Switching to a generic Kafka image (like apache/kafka) would break this volume mount because standard images do not use the /bitnami directory structure, forcing users to debug and rewrite the config.
Proposed Solution
I suggest switching to soldevelo/kafka:3.7.
This image is a free, drop-in replacement that preserves the /bitnami/kafka directory structure. This ensures the example runs "out of the box" for everyone without any configuration changes.
Suggested Change in README-google-microservices.md:
# Old
image: bitnami/kafka:3.7
# New
image: soldevelo/kafka:3.7
I can submit a Pull Request to update this reference. Would you be open to that?
Hi,
I noticed that the configuration example in
README-google-microservices.mdusesbitnami/kafka:3.7and specifically mounts a volume to/bitnami/kafka.The Problem
Bitnami has restricted public access to their Docker images. Users trying to run this standalone example will likely encounter
pull access deniederrors.Crucially, the configuration uses:
- kafka_data:/bitnami/kafkaSwitching to a generic Kafka image (like
apache/kafka) would break this volume mount because standard images do not use the/bitnamidirectory structure, forcing users to debug and rewrite the config.Proposed Solution
I suggest switching to
soldevelo/kafka:3.7.This image is a free, drop-in replacement that preserves the
/bitnami/kafkadirectory structure. This ensures the example runs "out of the box" for everyone without any configuration changes.Suggested Change in
README-google-microservices.md:I can submit a Pull Request to update this reference. Would you be open to that?