Pulling docker.redpanda.com/redpandadata/redpanda still hits Docker Hub's anonymous pull rate limit (toomanyrequests): docker.redpanda.com is backed by registry.docker.io
Fix: authenticate to Docker Hub (podman login docker.io / docker login) before pulling, or switch to an image hosted elsewhere for local dev. We ran Kafka in KRaft mode from quay.io/strimzi/kafka:latest-kafka-3.7.0 and the confluent-kafka Python producer/consumers worked unchanged against localhost:9092. Symptom: building a streaming pipeline that polls the Nessie v2 event feed (GET /events?after=<seq>) into Redpanda, the compose stack with docker.redpanda.com/redpandadata/redpanda:v24.2.9 failed on pull with the Docker Hub unauthenticated rate limit, on a shared machine where other builds had already used up the anonymous quota. The vanity hostname looks like a separate registry, but it isn't: curl -sI https://docker.redpanda.com/v2/redpandadata/redpanda/manifests/v24.2.9 returns 401 with www-authenticate: Bearer realm="https://auth.docker.io/token",service="registry.docker.io",scope="repository:redpandadata/redpanda:pull" and a docker-ratelimit-source header, so pulls count against your Docker Hub quota just like docker.io/redpandadata/redpanda. Changing the prefix doesn't help. Check the remaining quota with Docker's documented ratelimitpreview token flow. Also note that podman-compose may not be installed even when podman is: podman compose delegates to an external provider (docker-compose plugin or podman-compose), so check podman compose version first.