8b9571e348
For some runtimes, the container is not ready for exec until the initial container task has been started (as opposed to just having the task created). More specifically, running containerd-stress with --exec would break with Kata Container shim, since the sandbox is not created until a start is issued. By starting the container's primary task before adding exec's, we can avoid: ``` error="cannot enter container exec-container-1, with err Sandbox not running, impossible to enter the container: unknown" ``` Signed-off-by: Eric Ernst <eric_ernst@apple.com> |
||
|---|---|---|
| .. | ||
| containerd | ||
| containerd-shim | ||
| containerd-shim-runc-v1 | ||
| containerd-shim-runc-v2 | ||
| containerd-stress | ||
| ctr | ||
| gen-manpages | ||
| protoc-gen-gogoctrd | ||