how containerd interacts with runc

[huimxu]

哪位大神可以指点一下containerd是在哪里调用了runc create和runc start?
我在运行docker run -it [images] /bin/bash时，没有任何输出。。（正常情况下会打印root@container-id吧。。）直到我输入exit后退出容器时，我在容器里执行的所有的命令都打印出来了。
我猜想可能原因是在读写的时候堵塞了。。原因是runc create 完成之后，没有收到runc start的命令？

所以，有没有指导的。。。万分感谢！

[fuweid]

Hi, containerd will fork containerd-shim which will call runc create by Task.Create and runc start by Task.Start API.

No idea what happen in your case. If you have problem with docker run -it [image] /bin/bash, please check your entrypoint of image. Thanks

[mikebrow]

from google translate:

Who can tell me where containerd called runc create and runc start?
When I run 'docker run -it [images] /bin/bash, there is no output.'
Under normal circumstances, root@container-id will be printed.
Until I exit the container after typing exit, all the commands I executed
in the container are printed.

I guess the possible reason is that it is blocked when reading and writing. .
The reason is that after runc create is completed, the runc start command is not received?

So, is there any guidance. Many thanks!

docker run calls containerd for the create and start (which is what run does)..

It sounds like you want a prompt (-it) but you also want the container name.. try:
'docker run --name myContainerName --rm -i -t [image] bash'