Kubespray: CRIO setup with calico: docker not found error

Created on 23 Dec 2018 · 9Comments · Source: kubernetes-sigs/kubespray

Environment:

Bare metal, preconfigured with ssh access

OS:

Both Host and Kube-hosts: Centos 7(>=7.4)

Version of Ansible (ansible --version):
ansible 2.7.5
config file = /mnt/src/ansible/ansible.cfg
configured module search path = [u'/mnt/src/ansible/kubespray/library']
ansible python module location = /usr/lib/python2.7/site-packages/ansible
executable location = /usr/bin/ansible
python version = 2.7.5 (default, Jul 13 2018, 13:06:57) [GCC 4.8.5 20150623 (Red Hat 4.8.5-28)]

Kubespray version (commit) (git rev-parse --short HEAD):
2f5c0d10bb121a23f38530d67f27f058eacc3653

Network plugin used:
calico

Copy of your inventory file:

[kube]
kube1.company.loc

[kube-node:children]
kube

[k8s-cluster:children]
kube

[etcd:children]
kube

[kube-master:children]
kube

[kubespray:children]
kube

Command used to invoke ansible:
ansible-playbook -i hosts -l kube ./site.yml

Output of ansible run:
https://gist.github.com/altmind/9a901c06dc853c8482843b75c955bb5f#file-ansible-out-txt

I want to run kubespray with KRIO while integrating kubespray in existing ansible environment.
I got 1 kubernetes host: kube1.company.loc that belongs to group kube

I've followed the steps to integrate kubespray in existing ansible and then copied all.yml -> group_vars/kube.yml and k8s-cluster.yml -> group_vars/k8s-cluster.yml to local ansible workspace.
You can see my inventory above.

I've followed the steps to use KRIO instead of docker:
group_vars/kube

download_container: false
skip_downloads: false

group_vars/k8s-cluster

etcd_deployment_type: host
kubelet_deployment_type: host
helm_deployment_type: host
container_manager: crio

Thank you for fixing #3925, I was able to go further in deployment process. However, now i get "docker binary is missing" down below in the workflow - in "network_plugin/calico : Calico | Copy cni plugins from calico/cni container" step with the error fatal: [kube1.company.loc]: FAILED! => {"attempts": 4, "changed": false, "cmd": "/usr/bin/docker run --rm -v /opt/cni/bin:/cnibindir quay.io/calico/cni:v3.1.3 sh -c 'cp /opt/cni/bin/* /cnibindir/'", "msg": "[Errno 2] No such file or directory", "rc": 2}
I can cofirm that there is no /usr/bin/docker on the bare metal machine. There are crioctl and runc available though.

Source

altmind

Most helpful comment

Still an issue

altmind on 10 Jun 2019

👍3

All 9 comments

How about we install anduse libpod/podman if we are running without docker tools?
Podman should be enough to run this container once to export the cni plugins.

altmind on 28 Dec 2018

👍2

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 on 11 Apr 2019

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 on 11 May 2019

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

fejta-bot on 10 Jun 2019

@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.