Thursday, 2022-02-24

kata-irc-bot<eric.ernst> FRIENDS OF KATA -- I'm planning on cutting RC0 for 1.4 release *very* soon.  If you have a feature that you're hoping to be part of 1.4 that isn't merged yet, please let me know so we can track, and I can help you get it in.  If your changes aren't merged by ~EOD Friday, you probably won't make it into release (planned 2/28).00:07
kata-irc-bot<eric.ernst> Similarly, if you landed a fix and have been lazy on backport, please finish this before end of week!00:08
kata-irc-bot<eric.ernst> its happening00:09
kata-irc-bot<eric.ernst> cross post --> https://katacontainers.slack.com/archives/C879ACQ00/p164566121873814900:17
kata-irc-bot<fighterhitx> Hi, I found that the kata binary I compiled was using `/usr/share/defaults/kata-containers/configuration.toml` , but the kata binary installed by the tarball was using `/opt/kata/share/defaults/kata-containers /configuration.toml`, how is this determined?02:10
kata-irc-bot<eric.ernst> there's a good link for this -- digging...02:14
kata-irc-bot<eric.ernst> https://github.com/kata-containers/kata-containers/blob/main/src/runtime/README.md#configuration-file-location02:14
kata-irc-bot<fighterhitx> Thank you @eric.ernst. I read the docs just now, but I'm still a bit confused, why the binaries in the *tarball* use the config files under `/opt/kata/share/`, because I haven't configured anything, is it because the config has been compiled into the binaries? ?02:43
kata-irc-bot<eric.ernst> • In your case, I'm guessing you're hitting the second point:  ```The containerd shimv2 options passed to the runtime.``` 03:42
kata-irc-bot<eric.ernst> If you're using containerd, you will see that there are runtime options defined for kata, including the config path03:42
kata-irc-bot<eric.ernst> IIRC there is similar in place for CRIO as well.03:42
kata-irc-bot<chongjinheng> Hi all, I'm trying out the memory hotplug feature in kata. https://github.com/kata-containers/kata-containers/blob/main/docs/how-to/how-to-hotplug-memory-arm64.md  As I understand the steps in the documentation happens during the container start time when we do `ctr run ....`  Is there any document that I can refer to on how to do it with Kubernetes?  Appreciate your help, thanks!04:23
kata-irc-bot<fidencio> @bergwolf, oh, interesting, I thought we were intentionally disabling it06:42
kata-irc-bot<bergwolf> @fidencio But why? I don't think we can choose what kind of container is running on top of kata.07:32
kata-irc-bot<fidencio> @bergwolf, I think you understood me wrong.  I totally agree it doesn't make much sense to have that disabled, I just though it was, for a reason I cannot understand, disabled by default.07:33
kata-irc-bot<fidencio> Anyways, as I have that patch already, let me also submit that upstream Today07:34
kata-irc-bot<bergwolf> Cool! I totally agree we should enable it by default.07:34
kata-irc-bot<bergwolf> Just run a regular pod with memory resource limits. Then it will be launched using memory hotplug by kata.07:57
kata-irc-bot<chongjinheng> Thank you @bergwolf!08:25
kata-irc-bot<fidencio> @bergwolf, https://github.com/kata-containers/kata-containers/pull/376008:26
kata-irc-bot<eric.ernst> Ah, perhaps it is using KATA_CONF_FILE then -- can you stat /usr/local/bin/containerd-shim-kata-v2 ?  It may be a bash script that sets KATA_CONF_FILE env variable and then calls /opt/kata/bin/containerd-shim-kata-v2 ?16:02

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