Monday, 2020-07-13

kata-irc-bot1<bergwolf> @saini.paramdeep Depend on how you plan to check it (e.g., by scripts? by container process itself? by command lines? by devops monitoring tools?). For example, a pretty simply way, if you can exec into the container, you can check it by comparing the kernel version between the container and the host with command like `uname -r` .03:20
kata-irc-bot1<saini.paramdeep> @bergwolf Yes and I do agree this is one of the best way.03:21
*** bpradipt has joined #kata-general04:19
*** bpradipt has quit IRC04:19
*** sameo_ has joined #kata-general04:41
*** bpradipt has joined #kata-general04:52
*** sgarzare has joined #kata-general06:59
*** sameo_ has quit IRC08:10
*** sameo has joined #kata-general08:22
*** sgarzare has quit IRC09:06
*** sgarzare has joined #kata-general09:09
kata-irc-bot1<georg.kunz> @fidencio Hi, good morning. I think you pointed me to using annotations to set a specific kernel and image per sandbox, right? I have been trying to use annoations as per https://github.com/kata-containers/documentation/blob/master/how-to/how-to-set-sandbox-config-kata.md but they just don’t get picked up at runtime… I did specify pod_annotations = [“io.katacontainers.*“] in the containerd config, but to no success. Anyth09:13
kata-irc-bot1I can check?09:13
*** sgarzare has quit IRC09:59
*** sgarzare has joined #kata-general12:09
*** pvdp66556 has quit IRC12:34
kata-irc-bot1<fidencio> Heya! Sorry, I missed your message earlier Today13:26
kata-irc-bot1<fidencio> Basically, here's the documentation for the annotations: https://pkg.go.dev/github.com/kata-containers/runtime/virtcontainers/pkg/annotations?tab=doc13:26
kata-irc-bot1<fidencio> @christophe, as you were playing with the annotations recently, mind giving some input here?  @georg.kunz, please, mind that IIRC Christophe is on vacation for the next day days.13:27
*** bpradipt has quit IRC13:27
*** th0din_ has quit IRC13:27
*** irclogbot_1 has quit IRC13:27
*** bpradipt has joined #kata-general13:28
*** th0din_ has joined #kata-general13:28
*** irclogbot_1 has joined #kata-general13:28
kata-irc-bot1<georg.kunz> hi, thank you for pinging the right people! One more thing: I re-created my setup on Ubuntu 18.04 while I had issues on 16.04. on 18.04 everything works nicely out of the box, which is fine for me13:30
kata-irc-bot1<georg.kunz> I have to admit that I ran into some more issues with 16.04. It is still listed as a supported distribution, but it seems not to getting so much test coverage?13:30
kata-irc-bot1<fidencio> Hmm. I sincerely think we should drop support to old distros, and document better what we support with which version of kata.13:46
kata-irc-bot1<fidencio> Yeah, let's bring this up on our meeting Tomorrow. What do you think?13:46
kata-irc-bot1<georg.kunz> yes, fine. I can mention the issues I saw15:02
kata-irc-bot1<fidencio> I mean, dropping support to those old OSes :slightly_smiling_face:15:46
*** sgarzare has quit IRC16:01
*** th0din has joined #kata-general19:14
*** th0din_ has quit IRC19:15
kata-irc-bot1<archana.m.shinde> @fidencio Add it to the agenda for tomorrow :)20:56
*** pvdp66556 has joined #kata-general20:59
kata-irc-bot1<fidencio> Thanks!21:01
kata-irc-bot1<christophe> @georg.kunz Here is an example of what annotations would look like in your manifest: ```apiVersion: v1 kind: Pod metadata:   name: annotation   labels:     app: annotation   annotations:     io.katacontainers.config.hypervisor.virtio_fs_daemon: "/usr/local/bin/hello"     io.katacontainers.config.hypervisor.virtio_fs_extra_args: "[ \"-o\", \"xattr\" ]" #    io.katacontainers.config.hypervisor.virtio_fs_daemon: "/usr/sbin/poweroff"21:09
kata-irc-bot1 spec:   runtimeClassName: kata   containers:     - name: jenkins-kata [... the rest as usual ... ]```21:09
*** th0din has quit IRC23:36
*** th0din has joined #kata-general23:41

Generated by irclog2html.py 2.17.2 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!