Friday, 2020-04-03

*** errordeveloper has joined #kata-dev00:27
*** errordeveloper has quit IRC00:32
*** errordeveloper has joined #kata-dev02:28
*** errordeveloper has quit IRC02:34
*** errordeveloper has joined #kata-dev04:29
*** errordeveloper has quit IRC04:34
*** sameo has joined #kata-dev05:00
*** errordeveloper has joined #kata-dev06:03
*** errordeveloper has quit IRC06:08
*** igordc has quit IRC06:21
*** errordeveloper has joined #kata-dev06:21
*** jodh has joined #kata-dev06:42
*** jugs has quit IRC07:00
*** jugs has joined #kata-dev07:00
*** dklyle has quit IRC07:08
*** sgarzare has joined #kata-dev07:21
*** davidgiluk has joined #kata-dev08:03
*** gwhaley has joined #kata-dev08:07
*** ailan has joined #kata-dev08:20
*** devimc has joined #kata-dev13:00
*** crobinso has joined #kata-dev13:11
*** crobinso has quit IRC13:46
*** devimc has quit IRC14:11
*** devimc has joined #kata-dev14:12
*** dklyle has joined #kata-dev15:09
*** kata-irc-bot1 has quit IRC15:15
*** kata-irc-bot has joined #kata-dev15:18
*** igordc has joined #kata-dev15:32
*** crobinso has joined #kata-dev15:49
kata-irc-bot<fidencio> @archana.m.shinde, I may be missing some really basic knowledge about configuring shimv216:31
kata-irc-bot<fidencio> When I try to start a pod using kata-qemu, using OpenShift, the pod is scheduled but never started16:31
kata-irc-bot<fidencio> Not sure whether I'm missing to have something started on the host16:32
gwhaley@fidencio: is it telling you anything in the logs for the failed pod?16:35
gwhaleyI use kata-deploy to deploy shimv2 on containerd - you can maybe reference what the kata deploy script does to the node to see how it sets it up, if really stuck16:35
*** pcaruana has quit IRC16:37
kata-irc-bot<archana.m.shinde> @fidencio yes, do the logs or a describe on the pod reveal anything?16:41
kata-irc-bot<archana.m.shinde> iirc, you just need this in your crio config file ```[crio.runtime.runtimes.kata-qemu] runtime_path = "/path/to/containerd-shim-kata-v2" runtime_type = "vm"```16:42
kata-irc-bot<fidencio> That's exactly how my config looks like16:43
kata-irc-bot<fidencio> Which logs shall I look for?16:43
kata-irc-bot<archana.m.shinde> kubectl logs $pod or kubectl describe $pod , does not reveal much?16:44
kata-irc-bot<archana.m.shinde> you have the runtimeclass applied right?16:44
kata-irc-bot<fidencio> I have the runtime class applied16:45
kata-irc-bot<fidencio> oc describe pod $pod only shows me totally events that failed16:46
kata-irc-bot<fidencio> And `Status:       Pending`16:46
*** sgarzare has quit IRC16:48
kata-irc-bot<fidencio> well, wait, those seem to be related: https://paste.centos.org/view/aa6731a016:48
*** devimc has quit IRC16:49
*** devimc has joined #kata-dev16:49
*** jodh has quit IRC17:00
kata-irc-bot<archana.m.shinde> yeah seems like a CNI issue there17:01
kata-irc-bot<fidencio> so, it may be related to kata17:06
kata-irc-bot<fidencio> I mean, the CNI issue may be something related to kata17:06
*** gwhaley has quit IRC17:07
kata-irc-bot<fidencio> Okay, fixed that changing `manage_network_ns_lifecycle` to `false`17:48
kata-irc-bot<fidencio> still facing some issues, but I'll try debugging with OpenShift team firstly17:48
kata-irc-bot<fidencio> Thanks for the help!17:48
kata-irc-bot<fidencio> @archana.m.shinde, seems that CRI-O doesn't explicitly set CNI_NETNS, but somehow kata expects it to be set: ```Failed to create pod sandbox: rpc error: code = Unknown desc = failed to create pod network sandbox k8s_example_default_60be65fe-af7b-4091-a37d-5ada927f1e89_0(ae22fda701a87190bf7d88903a9127a355c0c6a77987fca00bde16c757f959f3): required env variables [CNI_NETNS] missing```17:52
*** errordeveloper has quit IRC18:32
*** errordeveloper has joined #kata-dev19:00
*** errordeveloper has quit IRC19:05
kata-irc-bot<philip.schmidt> Hey all, is there a way to nsenter into a kata container if a container is priviliged? I notice https://github.com/kata-containers/runtime/blob/master/virtcontainers/pkg/nsenter/nsenter.go bus wasnt sure if will be any different to nsenter which doesnt properly nsenter into the actual kata container...19:15
*** davidgiluk has quit IRC19:49
*** crobinso has quit IRC20:00
kata-irc-bot<fidencio> JFTR, I may have hit a bug in crio, I will keep debugging this on Monday, too late, even for me.20:38
*** errordeveloper has joined #kata-dev21:01
*** sameo has quit IRC21:01
*** errordeveloper has quit IRC21:06
*** errordeveloper has joined #kata-dev21:51
*** devimc has quit IRC22:02
*** igordc has quit IRC22:36
*** igordc has joined #kata-dev22:36
*** ailan has quit IRC23:08

Generated by irclog2html.py 2.15.3 by Marius Gedminas - find it at mg.pov.lt!