Don't call runc start when restoring a checkpoint (#302)
Don't call runc start when restoring a checkpoint (#302)

The create/start split left checkpoint/restore broken in that the create
side was calling runc restore, which fully restores the process to
operation, leaving a call to `runc start` as an error (process already
started). This patch skips process.Start as it is an unnecessary (and
wrong) step for a restored checkpoint.

Signed-off-by: Phil Estes <dbac1f450dc8326caa7ba104b384a0eca642250c@linux.vnet.ibm.com>
containerd/containerd,thaJeztah/containerd,dmcgowan/containerd,thaJeztah/containerd,rajasec/containerd,estesp/containerd,chanezon/containerd,crosbymichael/containerd,lichao-mobanche/containerd,mikebrow/containerd,Wolphin-project/containerd,containerd/containerd,crosbymichael/containerd,miaoyq/containerd,dmcgowan/containerd,vdemeester/containerd,mikebrow/containerd,kunalkushwaha/containerd,estesp/containerd,yuexiao-wang/containerd,vdemeester/containerd,miaoyq/containerd,AkihiroSuda/containerd,docker/containerd,kunalkushwaha/containerd,hqhq/containerd,xiekeyang/containerd