Deploy calico failed when use cri-o runtime

[riverzhang]

https://github.com/kubernetes-incubator/kubespray/blob/master/roles/network_plugin/calico/tasks/install.yml#L38
https://github.com/kubernetes-incubator/kubespray/blob/master/roles/network_plugin/calico/tasks/install.yml#L49

Doesn't use docker run.
What other methods to do that?

[riverzhang]

cc @okamototk

[riverzhang]

/assign @Atoms @mattymo

[Atoms]

i suggest that we should switch then to calicoctl binary

[ant31]

can we run containers with cri-tools:
https://github.com/kubernetes-sigs/cri-tools

and continue to have the same workflow ?

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[fejta-bot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten

[fejta-bot]

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

[k8s-ci-robot]

@fejta-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.