CP Docker Images shipped with staging-confluent-packages in their yum/apt config will be broken.

Customers running update routines with the yum/apt package managers inside the cp-docker-images will run into HTTP 4xx issues from confluent-hosted infrastructure. You may find an example public report here:

https://github.com/confluentinc/kafka-images/issues/106

Customers running “older” cp-docker images (Older meaning those that were published before September 30th)

cp-docker-images ship with yum/apt configuration on their file systems that allow the docker OS package manager to install Confluent Platform OS packages from HTTP endpoints. Some docker images were released that referenced https://s3-us-west-2.amazonaws.com/staging-confluent-packages-${VERSION}. This was Confluent Release Engineering’s mistake.

Release Engineering has:

• Rebuilt all “latest” patch releases (2021 Q3 patch releases, ie: 6.2.1, 6.1.3, 6.0.4, etc.) with fixed yum/apt configuration pointing to https://packages.confluent.io

• Repaired all impacted images and pushed a new layer that corrects this issue.

The preferred resolution is to take the latest tagged docker image for their release. For example, if the customer was running docker image tag 6.2.0 and encountering this issue, it means they’re usign an older revision (likely 6.2.0-1), they should instead use the update 6.2.0 tag (A 6.2.0-10 revision tag will also have been pushed).

Alternatively, as a "work around" customers can apply directly to their running containers or derived images:

• Remove the offending config (Either the /etc/yum.repos.d/confluent.repo for RHEL-based images or the applicable line in /etc/apt/sources.list for debian-based images)

• Fix the offending config to point to https://packages.confluent.io/...

• Use package manager options to disable the offending repo (ie: yum --disablerepo='Confluent*' ...)