jokemanfire

> Just to make sure I understand — currently, unless the debug flag is set to true, when pulling an image, ctr displays pull data to stdout, correct? > >...

hello,I pushed this pr to meet this requirement.[https://github.com/containerd/containerd/pull/9672](url)

I think the original purpose is to avoid printing data during debugging. Maybe it is incorrect to modify this code directly.

> Please note that ctr is an [unsupported development-focused tool](https://containerd.io/releases/#ctr-tool) and is not recommended as a general-purpose client. > > If you wish to suppress the output, how about redirecting...

> I think we have the same problem #10134 The questions all caused by not tar format data. But this is a feature for container import gzip is not same...

I think it is the same problem. test environment: containerd 1.7.11 rustshim latest test function: containerd : TestContainerDrainExecIOAfterExit It will exec exceed the time, and it will report a fail.In...

Hi @fuweid @Burning1020 @abel-von I try to resolve this problem in rust-shim at the beginning . But I think use fifo directly can reduce the copy-io 's performance loss now...

How about try to use copy-io first , it may not same with go-shim to implementation copy-io @Burning1020 . I will try to do this thing, resolve issues that differ...

Thanks for your patience , I know that the process is runc to start that , and hold the fifo write (such like `sh -c sleep 365d`), But I don't...

> > Thanks for your patience , I know that the process is runc to start that , and hold the fifo write (such like sh -c sleep 365d), But...