Hi,
I noticed that both docker/docker-compose.kafka.yml and docker-edge/docker-compose.yml reference images from the bitnamilegacy namespace (versions 4.0 and 3.8.1).
The Problem
Relying on a repository explicitly named bitnamilegacy is not ideal for a production-grade IoT Edge platform. These images are often intended as temporary stopgaps, may not receive consistent security patches, and their long-term availability is not guaranteed compared to actively maintained upstream sources.
Proposed Solution
I suggest switching to soldevelo/kafka.
This image is an actively maintained, free drop-in replacement. It is built to preserve the standard Bitnami configuration structure (environment variables, paths, scripts), so your existing Compose setups will continue to work without modification, but backed by a stable, non-legacy source.
Suggested Changes:
In docker/docker-compose.kafka.yml:
# Old
image: "bitnamilegacy/kafka:4.0"
# New
image: "soldevelo/kafka:4.0"
Hi,
I noticed that both
docker/docker-compose.kafka.ymlanddocker-edge/docker-compose.ymlreference images from thebitnamilegacynamespace (versions 4.0 and 3.8.1).The Problem
Relying on a repository explicitly named
bitnamilegacyis not ideal for a production-grade IoT Edge platform. These images are often intended as temporary stopgaps, may not receive consistent security patches, and their long-term availability is not guaranteed compared to actively maintained upstream sources.Proposed Solution
I suggest switching to
soldevelo/kafka.This image is an actively maintained, free drop-in replacement. It is built to preserve the standard Bitnami configuration structure (environment variables, paths, scripts), so your existing Compose setups will continue to work without modification, but backed by a stable, non-legacy source.
Suggested Changes:
In
docker/docker-compose.kafka.yml: