stop container will always timeout

[lifupan]

Description of problem

The containerd cri testcase will always failed on the following case:

[AfterEach] runtime should support basic operations on container
  /home/fupan/go/src/github.com/kubernetes-sigs/cri-tools/pkg/validate/container.go:76
STEP: stop PodSandbox
STEP: delete PodSandbox
[AfterEach] [k8s.io] Container
  /home/fupan/go/src/github.com/kubernetes-sigs/cri-tools/pkg/framework/framework.go:51

• Failure [62.259 seconds]
[k8s.io] Container
/home/fupan/go/src/github.com/kubernetes-sigs/cri-tools/pkg/framework/framework.go:72
  runtime should support basic operations on container
  /home/fupan/go/src/github.com/kubernetes-sigs/cri-tools/pkg/validate/container.go:68
    runtime should support stopping container [Conformance] [It]
    /home/fupan/go/src/github.com/kubernetes-sigs/cri-tools/pkg/validate/container.go:100

    Apr  7 23:49:43.344: stop container "4ec2bb2169b561e919f1b6d395edc1b46e92e104bec85f0b47f8fd2290ff5849" timeout.
    

    /home/fupan/go/src/github.com/kubernetes-sigs/cri-tools/pkg/validate/container.go:354

After some investigation, I found the root cause is as below:
When the testcase start a container successfully, it will then send a "SIGTERM" signal to stop this container, but at the same time, the container process hasn't been start completely, which means this init process is sleeping in exec syscall, thus this process hasn't install any handlers for SIGTERM signal, thus it will ignore "SIGTERM" signal sent to it.

Expected result

stop container should successfully.

Actual result

(replace this text with details of what actually happened)

---

(replace this text with the output of the kata-collect-data.sh script, after
you have reviewed its content to ensure it does not contain any private
information).