9d6acbee92
PR #18590 caused compatibility issues with registries such as gcr.io which support both the v1 and v2 protocols, but do not provide the same set of images over both protocols. After #18590, pulls from these registries would never use the v1 protocol, because of the Docker-Distribution-Api-Version header indicating that v2 was supported. Fix the problem by making an exception for the case where a manifest is not found. This should allow fallback to v1 in case that image is exposed over the v1 protocol but not the v2 protocol. This avoids the overly aggressive fallback behavior before #18590 which would allow protocol fallback after almost any error, but restores interoperability with mixed v1/v2 registry setups. Fixes #18832 Signed-off-by: Aaron Lehmann <aaron.lehmann@docker.com> |
||
|---|---|---|
| .. | ||
| fixtures/validate_manifest | ||
| metadata | ||
| xfer | ||
| pull.go | ||
| pull_v1.go | ||
| pull_v2.go | ||
| pull_v2_test.go | ||
| pull_v2_unix.go | ||
| pull_v2_windows.go | ||
| push.go | ||
| push_v1.go | ||
| push_v2.go | ||
| push_v2_test.go | ||
| push_v2_unix.go | ||
| push_v2_windows.go | ||
| registry.go | ||
| registry_unit_test.go | ||