Monday, 2021-06-07

kata-irc-bot<eric.ernst> I expect 1.5.2 to work.03:46
kata-irc-bot<eric.ernst> There really shouldn't be that tight of a coupling between containerd and Kata -- the shim-v2 API hasn't moved much...03:46
kata-irc-bot<david_hay> Hmmm, have tried it on two clusters, but with the same `NotFound` error - will dig around a bit more when time allows04:29
kata-irc-bot<eric.ernst> ok. I assume it's working fine in that cluster w/ out runtimeclass specified (ie, runc?)?04:30
kata-irc-bot<david_hay> Pretty sure but will double-check, in case I borked something else with my fat-fingered tinkering !04:33
*** fgiudici has joined #kata-general06:47
kata-irc-bot<santhosh.parampottupa> @eric.ernst I tried the below command and its working and the /proc/version is different from my host machine  `*santhosh_cameo@san-ka-test*:*~*$ sudo ctr run --runtime io.containerd.run.kata.v2 -t --rm docker.io/library/busybox:latest hello sh` `/ # cat /proc/version` `Linux version 5.4.60-52.container (abuild@lamb70) (gcc version 7.3.0 (Ubuntu 7.3.0-16ubuntu3)) #1 SMP Sat Jan 16 05:49:34 UTC 2021`07:25
kata-irc-bot<santhosh.parampottupa>07:29
*** jodh has joined #kata-general08:03
*** jodh has joined #kata-general08:04
kata-irc-bot<fupan> The latest containerd had switched the socket from abstract socket to unix path socket between containerd and shimv2, see https://github.com/containerd/containerd/commit/4a4bb851f5da563ff6e68a83dc837c7699c469ad , thus kata wouldn’t work on those containerds with that changes.09:47
kata-irc-bot<fupan> containerd break the backward compatibility.09:49
kata-irc-bot<david_hay> Ah, OK, that's good to know @fupan  Should we indicate a "known good" version of `containerd` in the Kata 2.0 docs ?  Looking at this as an example https://github.com/kata-containers/kata-containers/blob/main/docs/install/container-manager/containerd/containerd-install.md#install-containerd09:50
kata-irc-bot<david_hay> FYI the reason that I'm testing later versions of `containerd` is to try and get this working - https://github.com/kata-containers/kata-containers/pull/704  In other words, I want the sandbox/guest VM to have `/etc/resolv.conf` same as / similar to the host ( K8s node ) and running containers  TL;DR; I'm looking at a way to have the guest reach out to external services via their service / host name09:52
kata-irc-bot<david_hay> as per https://github.com/kata-containers/runtime/issues/160309:52
kata-irc-bot<fupan> we should document the best compatible containerd   in the doc, and I think we also need to update kata with the latest containerd vendor to make kata work on the latest containerd11:20
kata-irc-bot<fupan> I’ll  open file an issue on this and make a progress on fixing it.11:21
*** fuentess has joined #kata-general12:18
kata-irc-bot<david_hay> Perfect, please feel free to tag me on the issue - I'd love to help, if I can12:43
kata-irc-bot<fupan> I filed an issue https://github.com/kata-containers/kata-containers/issues/1971 to track this issue.12:57
*** devimc has joined #kata-general13:29
*** fuentess has quit IRC13:59
*** fuentess has joined #kata-general16:08
*** fuentess has quit IRC16:22
*** fgiudici has quit IRC16:25
*** fuentess has joined #kata-general16:58
*** jodh has quit IRC17:02
*** fuentess|2 has joined #kata-general17:26
*** fuentess has quit IRC17:30
*** fuentess has joined #kata-general21:06
*** fuentess|2 has quit IRC21:11
*** devimc has quit IRC22:03
*** fuentess has quit IRC22:35

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