This is a serious regression introduced recently.
Old ctr only uses 6 seconds to import the kube-apiserver tarball.
$ ctr version
Client:
Version: v1.2.6-38-g886002f5
Revision: 886002f5ab56302525d6f8f6aed274fb4d10bdec
Server:
Version: v1.2.0-774-gfdab4f47
Revision: fdab4f4789e2a7a0fa1f8c17a3cffc906505b547
WARNING: version mismatch
WARNING: revision mismatch
$ time ctr images import ~/kubernetes/kubernetes/server/bin/kube-apiserver.tar
unpacking k8s.gcr.io/kube-apiserver-amd64:v1.16.0-alpha.1.235_79e82a6345f4f3 (sha256:f563815a80b29432f1375761f984b1aae538d068544f8882829151fa5814fa79)...done
real 0m6.080s
user 0m1.880s
sys 0m0.357s
ctr from containerd HEAD needs >50 seconds.
$ time ../bin/ctr images import ~/kubernetes/kubernetes/server/bin/kube-apiserver.tar
unpacking k8s.gcr.io/kube-apiserver-amd64:v1.16.0-alpha.1.235_79e82a6345f4f3 (sha256:ca470514ce3c5b1d38be6ebe579c1e4e7c7873d113d6e6ee0620cdb69b963ef8)...done
real 0m56.965s
user 0m39.295s
sys 0m22.216s
This is a serious regression introduced recently.
Old ctr only uses 6 seconds to import the kube-apiserver tarball.
ctrfrom containerd HEAD needs >50 seconds.