Fu Wei

Hi @timshannon just want to confirm that the issue show up after the host or vm where the process run has been restarted? Thanks

sorry @timshannon for the confusion. I should ping @timannguyen

@Cindia-blue could you please use rebase instead of merge? and also, please squash into few commits. thanks!

> ctr: failed to read expected number of bytes: unexpected EOF I think it might be related to your registry. Would you mind to use debug mode to rerun it...

> layer-sha256:f868ac632a6f7994c589ce631afb99014698a783e173144bf4740e318303e992: downloading |++++++++++++++++++++++++++++++++------| 214.0 Mi/250.5 MiB @charugarg2810 I think there is some wrong with this blob. Would you mind to use `ctr -n k8s.io leases delete` leaky lease first...

> On some retries (~ 10-15 times) it gets auto-resolved. So, I think it maybe related to your registry. :(

REF: https://github.com/containerd/containerd/issues/8698#issuecomment-1594795093 cc @mikebrow @ruiwen-zhao

@payall4u would you send the whole goroutine dump log? thanks

@mattsains please rebase to fix CI issue. thanks!

@mattsains It needs @ahrtr 's approval. :)