What is the problem you're trying to solve
Context
I have a use case which uses the containerd client to pull and unpack container images from container registry. Recently had an experience where a storage hardware failure resulted in long image unpack times.
Problem
While the root cause was a hardware failure, the ask here is to enhance logging in the client to provide some more insight when these issues may be occurring.
Describe the solution you'd like
It would be nice to:
Additional context
My use case builds/runs containerd 1.6.x (LTS). I see tracing support is available in 1.7.x; however, was looking for a solution which doesn't require an upgrade away from LTS and less heavy handed than tracing. (Happy to receive feedback on this)
What is the problem you're trying to solve
Context
I have a use case which uses the containerd client to pull and unpack container images from container registry. Recently had an experience where a storage hardware failure resulted in long image unpack times.
Problem
While the root cause was a hardware failure, the ask here is to enhance logging in the client to provide some more insight when these issues may be occurring.
Describe the solution you'd like
It would be nice to:
image unpackedlogAdditional context
My use case builds/runs containerd 1.6.x (LTS). I see tracing support is available in 1.7.x; however, was looking for a solution which doesn't require an upgrade away from LTS and less heavy handed than tracing. (Happy to receive feedback on this)