Morning, we were about to release an upgrade to 0.8.34 to our live environment before realising the following:

> [config_kafka-setup stage-1 4/8] RUN mkdir -p /opt   && mirror=$(curl --stderr /dev/null <https://www.apache.org/dyn/closer.cgi?as_json=1> | jq -r '.preferred')   && curl -sSL "${mirror}kafka/2.8.1/kafka_2.13-2.8.1.tgz"   | tar -xzf - -C /opt   && mv /opt/kafka_2.13-2.8.1 /opt/kafka   && adduser -DH -s /sbin/nologin kafka   && chown -R kafka: /opt/kafka   && echo "===> Installing python packages ..."    && pip install --no-cache-dir jinja2 requests   && pip install --prefer-binary --prefix=/usr/local --upgrade "git+<https://github.com/confluentinc/confluent-docker-utils@v0.0.49>"   && echo "===> Applying log4j log4shell fix based on <https://www.slf4j.org/log4shell.html> ..."   && zip -d /opt/kafka/libs/log4j-1.2.17.jar org/apache/log4j/net/JMSAppender.class   && rm -rf /tmp/*   && apk del --purge .build-deps:
#0 0.853 tar: invalid magic
#0 0.853 tar: short read

https://dlcdn.apache.org/kafka/ It seems 2.8.1 of kafka has been removed since, a number of datahub versions may be affected as the version is hardcoded in the kafka-setup Dockerfile, thought it was worth flagging.

Hello Tiegsti, Kafka version 2.8.1 is an environment variable in the dockerfile which means you can override it during the build process.

Thanks, we’re making the amendments to our build job