Adds debug message per layer unpacking and adds duration field to
the existing image unpacking debug message.

Signed-off-by: Austin Vazquez <[email protected]>
(cherry picked from commit 01c4421)
Signed-off-by: Austin Vazquez <[email protected]>

Signed-off-by: Iceber Gu <[email protected]>
(cherry picked from commit 7f7ba31)
Signed-off-by: Iceber Gu <[email protected]>

Signed-off-by: Iceber Gu <[email protected]>
(cherry picked from commit 2e014fa)
Signed-off-by: Iceber Gu <[email protected]>

…7fd084cc0e7e8b45074b940f5c6bbdba

[release/1.7] Enhance container image unpack client logs

[release/1.7] cri: fix using the pinned label to pin image

The new active request is filed and there is no bytes read yet when the
progress reporter just wakes up. If the timeout / 2 is less than the
minPullProgressReportInternal, it's easy to file false alert.

We should remove the minPullProgressReportInternal limit.

Fixes: #8024

Signed-off-by: Wei Fu <[email protected]>

Signed-off-by: Wei Fu <[email protected]>

Close connection if no more data. It's to fix false alert filed by image
pull progress.

```
dst = OpenWriter (--> Content Store)

src = Fetch
        Open (--> Registry)
        Mark it as active request

Copy(dst, src) (--> Keep updating total received bytes)

   ^
   |  (Active Request > 0, but total received bytes won't be updated)
   v

defer src.Close()
content.Commit(dst)
```

Before migrating to transfer service, CRI plugin doesn't limit global
concurrent downloads for ImagePulls. Each ImagePull requests have 3 concurrent
goroutines to download blob and 1 goroutine to unpack blob. Like ext4
filesystem [1][1], the fsync from content.Commit may sync unrelated dirty pages
into disk. The host is running under IO pressure, and then the content.Commit
will take long time and block other goroutines. If httpreadseeker
doesn't close the connection after io.EOF, this connection will be
considered as active. The pull progress reporter reports there is no
bytes transfered and cancels the ImagePull.

The original 1-minute timeout[2][2] is from kubelet settting. Since CRI-plugin
can't limit the total concurrent downloads, this patch is to update 1-minute
to 5-minutes to prevent from unexpected cancel.

[1]: https://lwn.net/Articles/842385/
[2]: https://github.com/kubernetes/kubernetes/blob/release-1.23/pkg/kubelet/config/flags.go#L45-L48

Signed-off-by: Wei Fu <[email protected]>

[release/1.7] fix: ImagePull should close http connection if there is no available data to read.

Signed-off-by: ruiwen-zhao <[email protected]>

Add release notes for v1.7.10