confluent-kafka SchemaRegistryClient against Apicurio Registry: 404 'RESTEASY003210: Could not find resource for full path: .../subjects/<topic>-value/versions': use the /apis/ccompat/v7 base URL
Point every Confluent-style client at http://<host>:8080/apis/ccompat/v7, not at the bare registry root. Apicurio Registry (tested quay.io/apicurio/apicurio-registry-mem:2.6.2.Final) serves its Confluent Schema Registry compatible API under /apis/ccompat/v7 (v6 also answers); the root has no /subjects, so SchemaRegistryClient({'url': 'http://localhost:8080'}) with AvroSerializer fails on first produce with SchemaRegistryError RESTEASY003210: Could not find resource for full path: http://localhost:8080/subjects/nessie-events-value/versions?normalize=False (HTTP status code 404, SR code 404).
With {'url': 'http://localhost:8080/apis/ccompat/v7'} confluent-kafka 2.6.0 AvroSerializer registered subject nessie-events-value (schema id 1) and AvroDeserializer resolved it back by id with no local schema. Check quickly with curl http://localhost:8080/apis/ccompat/v7/subjects (returns [] on a fresh instance, 200) versus curl http://localhost:8080/subjects (404). The same base URL goes into kafka-ui as KAFKA_CLUSTERS_0_SCHEMAREGISTRY=http://<registry>:8080/apis/ccompat/v7.
Why people end up here: Redpanda's bundled registry is the usual hackathon choice, but docker.redpanda.com images hit Docker Hub's anonymous pull limit, ghcr.io/redpanda-data/redpanda returns 403 (Forbidden) on the bearer token request, and docker.io/vectorized/redpanda says requested access to the resource is denied. apache/kafka (KRaft) plus Apicurio from quay.io is a drop-in replacement that needs no Docker Hub pulls for the registry. The -mem image keeps schemas in memory, so schema ids reset on restart; already-written messages then point at ids the registry no longer knows.