Monday, 2018-09-03

*** zerocoolback has joined #kata-dev00:19
*** zerocoolback has quit IRC00:49
kata-irc-bot<xu> Both ok for me :slightly_smiling_face:02:31
*** zerocoolback has joined #kata-dev02:51
*** zerocoolback has quit IRC02:53
*** zerocoolback has joined #kata-dev02:54
*** zerocoolback has quit IRC03:54
kata-irc-bot<anne> Let’s plan to skip then. Cover things off via email. Sorry for the late notice—was traveling and got my dates mixed up! :)04:12
*** sjas_ has joined #kata-dev04:30
*** sjas has quit IRC04:33
*** zerocoolback has joined #kata-dev04:40
*** zerocoolback has quit IRC05:45
*** zerocoolback has joined #kata-dev05:49
*** zerocoolback has joined #kata-dev05:49
*** zerocoolback has quit IRC07:12
kata-irc-bot<james.o.hunt> @caoruidong - thanks!! :)07:58
*** davidgiluk has joined #kata-dev08:01
*** gwhaley has joined #kata-dev08:05
kata-irc-bot<james.o.hunt> @mvedovati - Morning!08:11
kata-irc-bot<mvedovati> @james.o.hunt hey :slightly_smiling_face:08:11
*** jodh has joined #kata-dev08:12
kata-irc-bot<james.o.hunt> @mvedovati - I'm just starting to look at the PR backlogs. Are there any particular areas / repos that interest you more than others?08:13
*** zerocoolback has joined #kata-dev08:15
kata-irc-bot<mvedovati> @james.o.hunt I am still trying to figure it out since my view on the whole project is limited. Anything you would suggest to start with?08:18
*** zerocoolback has quit IRC08:19
*** zerocoolback has joined #kata-dev08:20
kata-irc-bot<james.o.hunt> @mvedovati - I'd start by looking at the list of repos here and clicking "watch" so you get to see the github emails when issues are opened / PRs raised on each repo. Alternatively, you can open the kata-github slack channel if that works better for you. There is a more "human readable" summary of the repos here if that helps too: https://github.com/kata-containers/kata-containers08:20
*** zerocoolback has quit IRC08:21
*** zerocoolback has joined #kata-dev08:21
*** zerocoolback has quit IRC08:21
*** zerocoolback has joined #kata-dev08:22
kata-irc-bot<james.o.hunt> @mvedovati - if you haven't already done so, I'd also suggest installing kata and playing around with it a bit (https://github.com/kata-containers/documentation/tree/master/install). Once you've done that, you could try cloning the runtime repo, making a tiny change and then installing *your* version of the runtime on a test / dev system08:23
kata-irc-bot(https://github.com/kata-containers/documentation/blob/master/Developer-Guide.md#build-and-install-the-kata-containers-runtime). Another really interesting repo to start getting familiar with is osbuilder - try building a custom guest "mini O/S" image - it's really simple if you follow the steps in the dev guide (https://github.com/kata-containers/documentation/blob/master/Developer-Guide.md#create-and-install-rootfs-and-initrd-image).08:23
kata-irc-bot<james.o.hunt> @mvedovati - it's definitely worth enabling debug and seeing what that does too (https://github.com/kata-containers/documentation/blob/master/Developer-Guide.md#enable-full-debug, and https://github.com/kata-containers/tests/tree/master/cmd/log-parser).08:24
kata-irc-bot<james.o.hunt> But for a real "quick start" at PR reviews, you could take a look at the doc repo as there are some new PRs there, for example https://github.com/kata-containers/documentation/pull/238. For that one, you can of course just pick over the doc and look for typos, inconsistencies, and any sentences that are ambiguous / confusing. It's particularly valuable for non-native English speakers to help out with doc reviews by the way as the08:27
kata-irc-botdocs absolutely **must** be clear, correct, simple and unambiguous.08:27
kata-irc-bot<mvedovati> @james.o.hunt: thanks a lot. That's very helpful. I already played around with kata on my system. As you said I'll start go thru the PR and see if there's something I can help with.08:31
kata-irc-bot<james.o.hunt> @mvedovati - feel free to jump into any of the PRs - whatever looks interesting to you really.08:34
kata-irc-bot<james.o.hunt> @mvedovati - it's also instructive to look at logs when the CI failed for a PR. They can sometimes be quite big (up to 20M or so), but you can always download them in plain text format from Jenkins and use your favourite editor to view of course ;)08:35
kata-irc-bot<mvedovati> sure!08:36
*** zerocoolback has quit IRC08:45
*** zerocoolback has joined #kata-dev08:45
*** zerocoolback has quit IRC08:45
*** zerocoolback has joined #kata-dev08:46
*** zerocoolback has quit IRC08:46
*** zerocoolback has joined #kata-dev08:47
*** zerocoolback has quit IRC08:47
*** zerocoolback has joined #kata-dev08:47
*** zerocoolback has quit IRC08:48
*** zerocoolback has joined #kata-dev08:48
*** zerocoolback has quit IRC08:48
*** zerocoolback has joined #kata-dev08:49
*** zerocoolback has joined #kata-dev08:50
*** zerocool_ has joined #kata-dev08:51
*** zerocoolback has joined #kata-dev08:51
*** zerocoolback has quit IRC08:52
*** zerocoolback has joined #kata-dev08:52
*** zerocoolback has joined #kata-dev08:53
*** zerocoolback has quit IRC08:53
*** zerocoolback has joined #kata-dev09:33
*** zerocoolback has quit IRC09:56
*** sjas_ is now known as sjas10:37
kata-irc-bot<james.o.hunt> @mvedovati - nice review of https://github.com/kata-containers/documentation/pull/238 - thanks!10:52
kata-irc-bot<mvedovati> @james.o.hunt :+1:10:57
*** fuentess has joined #kata-dev12:04
*** zerocoolback has joined #kata-dev12:16
*** zerocoolback has quit IRC12:18
*** zerocoolback has joined #kata-dev12:18
*** zerocoolback has quit IRC12:45
*** zerocoolback has joined #kata-dev12:45
*** zerocoolback has quit IRC12:50
kata-irc-bot<niteshkonkar007> I am getting an error when launching a kata container, `docker: Error response from daemon: oci runtime error: Failed to connect to QEMU instance.`  What could be the possible solution? I have complied qemu from source.13:29
*** annabelleB has joined #kata-dev13:42
davidgilukniteshkonkar007: On a good day you can see some of the log messages in journal as qemu is started13:46
kata-irc-bot<ydjainopensource> @niteshkonkar007 it may mean the qemu instance failed to launch or immediately failed after launch..... I am experiencing similar bugs while porting to z13:48
kata-irc-bot<ydjainopensource> If you want you may use socat and check the boot log of the vm13:48
kata-irc-bot<niteshkonkar007> @ydjainopensource @davidgiluk: journalctl shows this in red `Sep 03 19:19:13 llmtul01b libvirtd[98115]: ethtool ioctl error: No such device` Let me investigate more ...13:50
davidgilukniteshkonkar007: Always look for the first error in there around the time you run it; there's always lots of stuff in the journal; the tricky bit is finding the important error!13:55
kata-irc-bot<niteshkonkar007> Ahh, there is an error before it. ` error="dial unix /run/vc/vm/9947b4df24ea386d1711cec4ad1f9734cc43eba3422f9f4e8c8324df8f6e942f/qmp.sock: connect: connection refused" name=kata-runtime`13:57
davidgilukniteshkonkar007: Can you see a line something like  kata-runtime....laynching qemu with: ....13:59
kata-irc-bot<ydjainopensource> Check the command which was generated and try running it on your cli.......This would hopefully allow you to pinpoint the issue14:00
*** annabelleB has quit IRC14:10
*** annabelleB has joined #kata-dev14:18
*** davidgiluk has quit IRC16:15
*** annabelleB has quit IRC16:26
*** tonyb has quit IRC16:31
*** annabelleB has joined #kata-dev16:33
*** dhellmann has quit IRC16:39
*** dhellmann has joined #kata-dev16:39
*** annabelleB has quit IRC16:43
*** dhellmann has quit IRC16:44
*** dhellmann has joined #kata-dev16:45
*** dhellmann has quit IRC16:54
*** dhellmann has joined #kata-dev16:54
*** jodh has quit IRC17:01
*** gwhaley has quit IRC17:20
*** fuentess has quit IRC18:55
*** fuentess has joined #kata-dev18:56
*** Wimpress has quit IRC19:10
*** jbryce has quit IRC19:10
*** jugs has quit IRC19:10
*** jugs has joined #kata-dev19:22
*** tonyb has joined #kata-dev20:51

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