kubernetes: k8s.gcr.io/coredns:1.1.3 is not built correctly.
We see this issue in containerd https://github.com/containerd/containerd/issues/2401.
It seems that the size in manifest of k8s.gcr.io/coredns:1.1.3 is wrong.
In the manifest list, the manifest size is 756:
$ curl -v -H 'Host:k8s.gcr.io' -H 'User-Agent:Go-http-client/1.1' -H 'Accept:application/vnd.docker.distribution.manifest.list.v2+json, *' -H 'Accept-Encoding:gzip' 'https://k8s.gcr.io/v2/coredns/manifests/sha256:9a239e9d3060aa5acd3d6e898fe405031594676e15e3b1b471f460eeef462583'
...
{
"mediaType": "application/vnd.docker.distribution.manifest.v2+json",
"size": 756,
"digest": "sha256:ab8aec91742937058f6b307efbd411ba8b49c5392a757431b00fda4bdd4fa588",
"platform": {
"architecture": "amd64",
"os": "linux"
}
},
...
However, the actual manifest size is 950:
$ curl -v -H 'Host:k8s.gcr.io' -H 'User-Agent:Go-http-client/1.1' -H 'Accept:application/vnd.docker.distribution.manifest.v2+json, *' -H 'Accept-Encoding:gzip' 'https://k8s.gcr.io/v2/coredns/manifests/sha256:ab8aec91742937058f6b307efbd411ba8b49c5392a757431b00fda4bdd4fa588' | wc -c
...
950
Docker doesn’t fail because it is not doing validation. However, containerd does validate it, and fails.
What tools did we use to build this image? /cc @thockin @kubernetes/sig-network-bugs /cc @dmcgowan
About this issue
- Original URL
- State: closed
- Created 6 years ago
- Comments: 31 (26 by maintainers)
re-pushed with manifest-tool and it seems good - please confirm
On Fri, Jun 22, 2018 at 12:39 PM Jeff Grafton notifications@github.com wrote:
/cc @ixdy Discussing this one offline.
It works now!
Thank you @vielmetti!