Closed zhangguanzhang closed 5 months ago
@neersighted @corhere PTAL
@zhangguanzhang Please take a look at why CI is failing
@zhangguanzhang Please take a look at why CI is failing
I found the reason and am modifying it locally. Also, can you help me look at another PR first? https://github.com/Mirantis/cri-dockerd/pull/349
@zhangguanzhang Please take a look at why CI is failing
I used the crictl create test on containerd with a non-existent sandbox ID and found an error. I thought the CreateContainer should have called the RunPodSandbox before it
$ crictl create fakeID container-config.json sandbox-config.json
E0420 23:37:56.581510 2865 remote_runtime.go:319] "CreateContainer in sandbox from runtime service failed" err="rpc error: code = NotFound desc = failed to find sandbox id \"aaa\": not found" podSandboxID="fakeID"
FATA[0000] creating container: rpc error: code = NotFound desc = failed to find sandbox id "fakeID": not found
@corhere @nevalla My local code tests are normal and I have added corresponding unit tests. PTAL
This feature is exactly what I want. Greate job. Hope this PR would be merged ASSP.
LGTM
@nwneisen Will this PR be cherry-picked into release/0.3
and included in the next release?
Not pushing for it, I just want to know if it makes sense to wait for a release, or if I should build from master
for now.
This is a new feature that I don't think is appropriate for cherry-pick into an existing branch. We're working on a 0.4 very shortly.
We're working on a 0.4 very shortly.
Any updates on this?
Fixes #111 . default-runtime is
runc
, You cannot useRuntimeClass.handler
to specify that the pod uses a non-runc runtime.:before
RuntimeClass.handler=docker
will used runcchange
handler: docker
tohandler: nvidia
will not work, but after this pr:will handle the
RuntimeClass.handler
work with crictl https://github.com/containerd/containerd/blob/main/docs/cri/crictl.md#run-a-pod-sandbox-using-a-config-file