By `docker build -t kuryr/cni:latest -f cni.Dockerfile . ` command to make a cni image, the resulting docker image fails to start.

Bug #1927885 reported by liujinxin on 2021-05-10
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
kuryr-kubernetes
Undecided
Unassigned

Bug Description

branch:stable/wallaby
By `docker build -t kuryr/cni:latest -f cni.Dockerfile . ` command to make a cni image, the resulting docker image fails to start.
run cni_ds_init Error logs:
```
+ cleanup
+ rm -f /etc/cni/net.d/10-kuryr.conflist
+ rm -f /opt/cni/bin/kuryr-cni
+ deploy
+ cp /kuryr-cni /opt/cni/bin/kuryr-cni
cp: cannot create regular file '/opt/cni/bin/kuryr-cni': No such file or directory
```

liujinxin (scilla) on 2021-05-10
description: updated
Revision history for this message
Maysa de Macedo Souza (maysa) wrote :

Hello,

I just tried updating cni image with wallaby branch, it worked fine.

Can you check if the CNI Pod is being mounted at "/opt/cni/bin"[1]?

[1] https://github.com/openstack/kuryr-kubernetes/blob/master/devstack/lib/kuryr_kubernetes#L685-L687

Revision history for this message
Michal Dulko (michal-dulko-f) wrote :

The kuryr-cni image is designed to be run as a Kubernetes pod with the CNI bin and configuration directories mounted at /opt/cni/bin and /etc/cni/net.d respectively.

liujinxin (scilla) on 2021-05-13
Changed in kuryr-kubernetes:
status: New → Invalid
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers