Monday, 2018-04-09

*** liujiong has joined #kata-dev02:48
*** sjas_ has joined #kata-dev04:34
*** sjas has quit IRC04:37
*** sameo has joined #kata-dev07:26
*** sameo has quit IRC07:37
*** gwhaley has joined #kata-dev08:01
*** cdent has joined #kata-dev08:39
*** sameo has joined #kata-dev08:40
*** liujiong has quit IRC09:33
*** sjas_ is now known as sjas09:36
kata-dev-irc-bot<bergwolf> @niteshkonkar007 https://github.com/kata-containers/agent/pull/210 should fix it. The error is because of unsupported netlink socket protocols. We should just specify what we need instead.10:10
kata-dev-irc-bot<niteshkonkar007> @bergwolf: Cool. Thnx10:23
kata-dev-irc-bot<niteshkonkar007> @bergwolf: I tested your patch. Works fine. ``` #sudo docker run -ti --runtime kata-runtime busybox sh Unable to find image 'busybox:latest' locally latest: Pulling from library/busybox f70adabe43c0: Already exists  Digest: sha256:58ac43b2cc92c687a32c8be6278e50a063579655fe3090125dcb2af0ff9e1a64 Status: Downloaded newer image for busybox:latest / # ls  bin   dev   etc   home  proc  root  sys   tmp   usr   var / # exit ```11:18
*** gwhaley has quit IRC12:23
kata-dev-irc-bot<bergwolf> thanks @niteshkonkar007!12:31
*** gwhaley has joined #kata-dev12:31
kata-dev-irc-bot<bergwolf> @niteshkonkar007 can you please also update this on https://github.com/kata-containers/documentation/pull/45 so that we can get the PR merged?12:33
*** mylinux has joined #kata-dev12:37
kata-dev-irc-bot<niteshkonkar007> @bergwolf: I have a comment here. https://github.com/kata-containers/documentation/pull/45#discussion_r17994050912:38
kata-dev-irc-bot<bergwolf> oops, sorry I missed it. I'll update now12:41
*** fuentess has joined #kata-dev12:43
kata-dev-irc-bot<bergwolf> @niteshkonkar007 updated. PTAL.12:49
*** devimc has joined #kata-dev13:07
kata-dev-irc-bot<niteshkonkar007> @bergwolf: Should this line "Create and install rootfs and initrd image" be "Create and install rootfs OR initrd image" as we are saying earlier "Configure to use initrd or rootfs image"? Or are we saying create and install both, but u can configure to use anyone of them.13:59
kata-dev-irc-bot<bergwolf> @niteshkonkar007 yes, we can install both and configure to use just one of them14:00
kata-dev-irc-bot<niteshkonkar007> @bergwolf: ``` script -fec 'sudo -E GOPATH=$GOPATH USE_DOCKER=true ./rootfs.sh ${distro}' If ${distro} is not set, it builds centos based rootfs by default.   ``` Are you sure it picks up centos by default? I get a list of supported distribution instead.14:03
kata-dev-irc-bot<bergwolf> oh, bad, the default is only in the osbuilder's Makefile and we are not depending on it in the dev guide!14:10
*** eernst has joined #kata-dev14:11
kata-dev-irc-bot<bergwolf> @niteshkonkar007 thanks for spotting that! I've updated the PR14:15
kata-dev-irc-botAction: bergwolf <-- a really bad doc writer :,)14:15
*** annabelleB has joined #kata-dev14:21
*** gabyc_ has joined #kata-dev14:28
kata-dev-irc-bot<niteshkonkar007> @bergwolf: LGTM :slightly_smiling_face:14:34
kata-dev-irc-bot<bergwolf> @niteshkonkar007 thanks for reviewing!14:37
*** annabelleB has quit IRC14:50
*** annabelleB has joined #kata-dev14:56
*** mylinux has quit IRC15:33
*** gabyc_ has quit IRC15:40
*** gabyc_ has joined #kata-dev15:42
*** gabyc_1 has joined #kata-dev15:43
*** gabyc_ has quit IRC15:43
*** fiddletwix has quit IRC15:44
*** fiddletwix has joined #kata-dev15:45
*** sameo has quit IRC16:02
*** mcastelino has joined #kata-dev16:08
*** Jeffrey4l has joined #kata-dev16:14
*** eernst has quit IRC16:25
*** eernst has joined #kata-dev16:49
*** annabelleB has quit IRC17:02
*** annabelleB has joined #kata-dev17:02
*** annabelleB has quit IRC17:15
*** annabelleB has joined #kata-dev17:21
*** gwhaley has quit IRC17:25
*** cdent has quit IRC18:40
*** cdent has joined #kata-dev18:47
*** smcginnis has left #kata-dev19:02
*** annabelleB has quit IRC19:07
*** annabelleB has joined #kata-dev19:11
*** eernst has quit IRC19:33
*** eernst has joined #kata-dev19:40
*** cdent has quit IRC19:45
*** eernst has quit IRC20:03
*** eernst has joined #kata-dev20:18
*** devimc has quit IRC20:57
*** annabelleB has quit IRC21:25
*** annabelleB has joined #kata-dev21:34
kata-dev-irc-bot<tallclair> Can someone explain to me or point me to how logging (specifically, stdout / stderr logging) is set up & works in Kata?21:36
kata-dev-irc-bot<tallclair> I.e. is it streamed out by the agent, written to disk, or proxied through a fd via 9p?21:37
kata-dev-irc-bot<sebastien.boeuf> the shim is responsible for STDIO. It constantly calls into the agent to retrieve all IO and display them on its own STDOUT/ERR21:40
kata-dev-irc-bot<sebastien.boeuf> @tallclair ^21:41
kata-dev-irc-bot<tallclair> What about multiple containers running in a single kata sandbox? Is there 1 shim & agent per runc container?21:42
kata-dev-irc-bot<tallclair> Or are the streams multiplexed?21:42
kata-dev-irc-bot<sebastien.boeuf> one shim per process21:47
kata-dev-irc-bot<archana.m.shinde> there is one shim per container21:47
*** fuentess has quit IRC21:47
kata-dev-irc-bot<sebastien.boeuf> per process21:47
kata-dev-irc-bot<archana.m.shinde> yeah rather process in a container21:47
kata-dev-irc-bot<sebastien.boeuf> and you have the proxy multiplexing this in case of serial connection21:48
kata-dev-irc-bot<archana.m.shinde> there is one agent per pod21:48
kata-dev-irc-bot<sebastien.boeuf> but in case of vsock, we won't need the proxy21:48
kata-dev-irc-bot<sebastien.boeuf> the protocol will handle the multiplexing21:48
kata-dev-irc-bot<sebastien.boeuf> @tallclair to be clear about the shim per process. I consider a process anytime you would do an exec on an existing container21:49
kata-dev-irc-bot<tallclair> got it, thanks!21:52
kata-dev-irc-bot<sebastien.boeuf> np !21:58
*** annabelleB has quit IRC21:59
*** gabyc_1 has left #kata-dev22:02
*** fuentess has joined #kata-dev22:35
*** annabelleB has joined #kata-dev22:57
*** sameo has joined #kata-dev23:03
*** sameo has quit IRC23:48

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