Hi @abel-von. Thanks for your PR.

I'm waiting for a containerd member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

The Usage of streaming io：
First, make sure you sandbox controller or shim implements Streaming API.
then add io_type of runtime in config.toml

[plugins."io.containerd.grpc.v1.cri".containerd.runtimes.vmm]
  runtime_type = "io.containerd.vmm.v1"
  sandboxer = "vmm"
  io_type = "streaming"

Then containerd will connect to the sandbox endpoint(the same address to serve Task API), and create streaming client to transfer the io stream. the id of the stream will be the the in the form of "-stdin", "-stdout", or "-stderr", id is either container id or exec id.

and in the CreateTaskRequest the Stdin will be in the form of streaming:<address>?protocol=<grpc/ttrpc>&id=<id>-stdout. then the Task API Service can get the stream id and get the created stream from the Streaming API Service, and copy ios from container to the stream.

@abel-von please rebase thanks

@abel-von please rebase thanks

done

@fuweid @abel-von FYI the config field for io_type is missing from the containerd config default output... It still works so far as defaulting to the io pipe mode.. but no indication of that is output.