Description
If a container from a Pod is deleted, it can no longer be created with the same configuration on Windows due to this error:
time="2021-02-26T14:36:42Z" level=fatal msg="creating container: rpc error: code = NotFound desc = failed to get sandbox container task: no running task found: task fd321b0a09e7d3509f4be47b8c043b174b8f16d2069b39f2837952ba1c17074c not found: not found"
This error can be observed while running the CRI integration test TestContainerRestart. The steps executed by the test are the same as the ones below.
Steps to reproduce the issue:
crictl --runtime-endpoint=npipe://./pipe/containerd-containerd pull docker.io/claudiubelu/pause:3.4.1
$POD_ID=(crictl --runtime-endpoint=npipe://./pipe/containerd-containerd runp .\pod.json)
$CONTAINER_ID=(crictl --runtime-endpoint=npipe://./pipe/containerd-containerd create $POD_ID .\container1.json .\pod.json)
crictl --runtime-endpoint=npipe://./pipe/containerd-containerd start $CONTAINER_ID
crictl --runtime-endpoint=npipe://./pipe/containerd-containerd stop $CONTAINER_ID
crictl --runtime-endpoint=npipe://./pipe/containerd-containerd rm $CONTAINER_ID
# the error occurs here on master:
$CONTAINER_ID=(crictl --runtime-endpoint=npipe://./pipe/containerd-containerd create $POD_ID .\container1.json .\pod.json)
pod.json:
{
"metadata": {
"name": "sandbox",
"namespace": "default",
"attempt": 1,
"uid": "hdishd83djaidwnduwk28bcsb"
},
"logDirectory": "/tmp"
}
container1.json:
{
"metadata": {
"name": "busybox"
},
"image":{
"image": "docker.io/claudiubelu/pause:3.4.1"
},
"command": [],
"args": []
}
Describe the results you received:
The last step will generate the following error:
time="2021-02-26T14:36:42Z" level=fatal msg="creating container: rpc error: code = NotFound desc = failed to get sandbox container task: no running task found: task fd321b0a09e7d3509f4be47b8c043b174b8f16d2069b39f2837952ba1c17074c not found: not found"
It is noteworthy that this error occurs with a containerd built from master. This error does not occur in version v1.4.3.
Describe the results you expected:
The opperation should have succeeded.
Output of containerd --version:
containerd github.com/containerd/containerd v1.5.0-beta.1-4-ge288feacf.m e288feacf35b202d483665fbd296113897427aca.m
This scenario works with the following containerd version:
containerd github.com/containerd/containerd v1.4.3 269548fa27e0089a8b8278fc4fc781d7f65a939b
Any other relevant information:
Description
If a container from a Pod is deleted, it can no longer be created with the same configuration on Windows due to this error:
This error can be observed while running the CRI integration test
TestContainerRestart. The steps executed by the test are the same as the ones below.Steps to reproduce the issue:
pod.json:
container1.json:
Describe the results you received:
The last step will generate the following error:
It is noteworthy that this error occurs with a
containerdbuilt from master. This error does not occur in versionv1.4.3.Describe the results you expected:
The opperation should have succeeded.
Output of
containerd --version:This scenario works with the following containerd version:
Any other relevant information: