| *** kata-irc-bot5 has joined #kata-general | 00:03 | |
| *** kata-irc-bot has quit IRC | 00:04 | |
| *** lpetrut has joined #kata-general | 06:00 | |
| *** sgarzare has joined #kata-general | 06:40 | |
| *** gwhaley has joined #kata-general | 08:04 | |
| kata-irc-bot5 | <alsotoes> Thanks @cesar.lara @jose.carlos.venegas.m for attending the (first) Kata Meetup yesterday in Mexico City.... sorry about the massive list of questions :) ... and we really apreciate the stickers @denise thanks for the community support!!!! | 12:49 |
|---|---|---|
| kata-irc-bot5 | <michael.zhao> Hello, I encountered an error when I tried to run a container with kata: docker run -it --runtime kata-runtime --privileged ubuntu bash | 14:06 |
| kata-irc-bot5 | <michael.zhao> docker: Error response from daemon: OCI runtime create failed: rpc error: code = Internal desc = Could not add route dest()/gw(172.17.0.1)/dev(eth0): network is unreachable: unknown. | 14:07 |
| kata-irc-bot5 | <michael.zhao> Anybody know what was wrong? | 14:07 |
| kata-irc-bot5 | <graham.whaley> @michael.zhao - see https://github.com/kata-containers/documentation/blob/master/Limitations.md#docker-run---privileged - kata does not (fully at leastg) support `--priv` - I'm going to guess that is related | 14:16 |
| kata-irc-bot5 | <michael.zhao> @graham.whaley, I tried without "--privileged", it was still the same | 14:27 |
| kata-irc-bot5 | <graham.whaley> thx @michael.zhao - that at least rules `--priv` out ;) I did a search on the kata github, and turned up this: https://github.com/kata-containers/runtime/issues/736#issuecomment-421998526, which then links off to a maybe related issue - which is around IPV6 - would you happen to be using/have IPV6 enabled? | 14:31 |
| kata-irc-bot5 | <graham.whaley> cc @eric.ernst @archana.m.shinde | 14:31 |
| kata-irc-bot5 | <michael.zhao> Thanks, but it doesn't look the same with my case. I am not using IPV6. And the detailed reason of issue 736 was "Could not add route dest(10.244.0.0/24)/gw()/dev(eth1): file exists". But in my case it was "network is unreachable". | 14:41 |
| kata-irc-bot5 | <michael.zhao> Does it mean the guest (Qemu VM) was not configured with a network? | 14:43 |
| *** lpetrut has quit IRC | 14:52 | |
| *** igordc has joined #kata-general | 14:57 | |
| *** lpetrut has joined #kata-general | 15:15 | |
| *** sgarzare has quit IRC | 15:38 | |
| kata-irc-bot5 | <jose.carlos.venegas.m> @michael.zhao so ` docker run -it --runtime kata-runtime ubuntu bash` fails due to a network error, is this a vanilla/fresh docker install or you are using a custom docker network configuration ? | 15:43 |
| kata-irc-bot5 | <niteshkonkar007> @jose.carlos.venegas.m: I have also faced this issue. When I debugged I realized there was no network in the VM when add network interface grpc request was taking place. Hence could not add route error. I was on a kubeadm+crio+runtimeclass cluster with weave/flannel as CNI. I moved to calico and the issue was not seen. | 16:16 |
| kata-irc-bot5 | <jose.carlos.venegas.m> @niteshkonkar007 yeah, I faced more network issues with some CNI configs. I am not sure if we have a list of "safe" cni pluings to use and documentation about limintations on some cases where the runtime is no able to replicate the network in the guest | 16:20 |
| kata-irc-bot5 | <jose.carlos.venegas.m> ^ @archana.m.shinde @manohar.r.castelino | 16:22 |
| kata-irc-bot5 | <jose.carlos.venegas.m> @michael.zhao could you open an issue to see if we are facing an issue like similar to something like that | 16:23 |
| kata-irc-bot5 | <jose.carlos.venegas.m> would be nice to see the command you use, docker version and probable docker logs | 16:24 |
| *** gwhaley has quit IRC | 17:00 | |
| *** igordc has quit IRC | 18:23 | |
| *** lpetrut has quit IRC | 19:02 | |
Generated by irclog2html.py 2.15.3 by Marius Gedminas - find it at mg.pov.lt!