feat: forward Accept header and fix Content-Type for Docker proxying #62

Merged
benvin merged 1 commits from benvin/docker-accept-header into master 2026-06-27 00:45:24 +10:00

1 Commits

Author SHA1 Message Date
unkinben dc34d6669d feat: forward Accept header and fix Content-Type for Docker proxying
ci/woodpecker/pr/build Pipeline failed
ci/woodpecker/pr/pre-commit Pipeline was successful
ci/woodpecker/pr/test Pipeline was successful
Two fixes for Docker registry compatibility:

1. Forward the client's Accept header to upstream registries. Docker
   clients send specific Accept headers to negotiate manifest format
   (Docker v2 vs OCI). Without forwarding, registries default to OCI
   format which older Docker daemons reject.

2. Always prefer upstream's Content-Type over the provider's default.
   The provider hardcodes manifest types but upstream may return a
   different format (e.g. OCI index vs Docker manifest list).

Tested with skopeo against DockerHub, GHCR, and Quay registries.
2026-06-27 00:43:00 +10:00