Wednesday, 2019-03-06

kata-irc-bot<xwlpt> @archana.m.shinde So if we pass the device via `-v device:device`, the device info will be exist in the req.devices and req.storages ?00:59
kata-irc-bot<archana.m.shinde> @xwlpt Yes01:00
kata-irc-bot<xwlpt> @archana.m.shinde thanks. I just found the code that add it to req.storages, but  when it  added to req.devices?01:01
kata-irc-bot<archana.m.shinde> @xwlpt Take a look at this: https://github.com/kata-containers/runtime/blob/master/virtcontainers/kata_agent.go#L103501:04
kata-irc-bot<xwlpt> `// Append container devices for block devices passed with --device.`01:04
kata-irc-bot<xwlpt> But  I pass it with `-v device:device`01:05
kata-irc-bot<xwlpt> I think if I use `-v device:device`, the info will only be exist at mounts info but not device info?01:06
kata-irc-bot<archana.m.shinde> No there will be device info as well for volumes that are block devices01:07
kata-irc-bot<archana.m.shinde> see this : https://github.com/kata-containers/runtime/blob/16bd9833876859b5e7fe09f42168899d2f2a7940/virtcontainers/container.go#L49401:08
kata-irc-bot<xwlpt> This is used to hotplug the device to the VM, and it will also add the device to c.devices ? And then handled by `ctrDevices = k.appendDevices(ctrDevices, c)` ?01:11
kata-irc-bot<xwlpt> I will have a check.01:12
kata-irc-bot<archana.m.shinde> @xwlpt Thats right01:12
kata-irc-bot<xwlpt> @archana.m.shinde Thanks for kindly help.01:13
kata-irc-bot<archana.m.shinde> @xwlpt sure, np.01:13
*** igordc has joined #kata-dev05:14
kata-irc-bot<xwlpt> @archana.m.shinde If the device attached manually, it should not appear in the mount ns of the container, but the question is why I can’t see it at the VM’s `/dev` directly?05:18
*** igordc has quit IRC05:27
*** igordc has joined #kata-dev06:07
*** igordc has quit IRC06:07
*** gmmaha has quit IRC07:10
*** gmmaharaj has joined #kata-dev07:11
*** gmmaharaj is now known as gmmaha07:11
kata-irc-bot<afrosi> Kata was installed by the scripts from tests. I need to check the combination that provokes that07:55
*** sgarzare has joined #kata-dev08:01
*** sameo has joined #kata-dev08:31
*** davidgiluk has joined #kata-dev08:59
*** gwhaley has joined #kata-dev09:03
*** jodh has joined #kata-dev09:17
*** sameo has quit IRC09:27
*** sameo has joined #kata-dev09:39
*** tmhoang has joined #kata-dev09:55
kata-irc-bot<xwlpt> @archana.m.shinde @eric.ernst Finally I found the device via ` nsenter -t 1 -m ls /dev/` in the VM. It is very interesting of this behavior. Why this is designed ?10:16
*** sgarzare has quit IRC10:32
*** sgarzare has joined #kata-dev10:32
*** devimc has joined #kata-dev13:09
*** fuentess has joined #kata-dev13:50
*** jugs1 is now known as jugs14:07
*** sameo has quit IRC14:14
*** sameo has joined #kata-dev14:50
kata-irc-bot<xwlpt> cc @eric.ernst15:03
*** lpetrut has joined #kata-dev15:50
*** sgarzare has quit IRC16:13
kata-irc-bot<jose.carlos.venegas.m> @eric.ernst @james.o.hunt@graham.whaley https://github.com/kata-containers/packaging/pull/345 I think we can skip the bump for the CI for this PR16:26
kata-irc-bot<jose.carlos.venegas.m> are you OK with it or prefer I bump and run CI again?16:26
kata-irc-bot<graham.whaley> If you didn't change anything that makes the kernel physically different (so, no change to kernel version, or config file, or make incovation etc.), then I think you are probalby OK. We've had some real activity in that repo and around that version file this past week or two.16:29
kata-irc-bot<graham.whaley> cc @salvador.fuentes ^^ coz we also discussed this on another PR like 5 minutes ago :slightly_smiling_face:16:30
kata-irc-bot<jose.carlos.venegas.m> agree16:32
kata-irc-bot<jose.carlos.venegas.m> we can force bump only for configs and patches directory16:33
kata-irc-bot<jose.carlos.venegas.m> so feel free to merge please16:34
kata-irc-bot<salvador.fuentes> Agree merging, is just an MD16:35
kata-irc-bot<eric.ernst> +116:52
*** lpetrut has quit IRC17:14
*** lpetrut has joined #kata-dev17:17
*** lpetrut has quit IRC17:32
*** jodh has quit IRC18:02
*** sameo has quit IRC18:05
*** irclogbot_0 has joined #kata-dev18:10
*** gwhaley has quit IRC18:21
*** sameo has joined #kata-dev18:34
*** irclogbot_0 has quit IRC18:36
*** sameo has quit IRC19:39
kata-irc-bot<eric.ernst> ping @gmmaharaj?20:07
kata-irc-bot<eric.ernst> you mentioned no changes needed for/etc/containerd/config.toml?20:07
*** igordc has joined #kata-dev20:10
kata-irc-bot<eric.ernst> @fupan - any updates on ```Based on the discussion in containerd/containerd#2916, the containerd configuration will have a field for runtime configuration files (likely to beconfig_file). However, the field is not available yet, and the shimv2 will search the configuration file in the default paths, same as kata-runtime cli): /etc/kata-containers/configuration.toml, /usr/share/defaults/kata-containers/configuration.toml. We will20:16
kata-irc-botupdate this document once the config_file field is available.``` from https://github.com/kata-containers/documentation/blob/master/how-to/containerd-kata.md#configuration20:16
*** davidgiluk has quit IRC20:17
*** igordc has quit IRC20:35
*** eernst has joined #kata-dev20:50
*** eernst has quit IRC20:52
*** eernst has joined #kata-dev20:52
*** eernst has quit IRC20:54
*** irclogbot_0 has joined #kata-dev21:07
kata-irc-bot<gmmaharaj> @eric.ernst yeah, without any config, if you pass `--runtime=io.containerd.run.kata.v2` it will look for containerd-shim-kata-v2 to handle the runtime.21:16
*** irclogbot_0 has quit IRC21:28
*** igordc has joined #kata-dev21:53
*** devimc has quit IRC22:09
*** irclogbot_0 has joined #kata-dev22:19
kata-irc-bot<eric.ernst> Could use feedback here: https://github.com/opencontainers/runtime-spec/issues/100222:24
kata-irc-bot<archana.m.shinde> @xwlpt Containers run in their own mount namespace, meant for isolating them. Thats why you see the behaviour.22:25
*** irclogbot_0 has quit IRC22:34
*** irclogbot_0 has joined #kata-dev22:35
*** fuentess has quit IRC22:36
*** irclogbot_0 has quit IRC22:44

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