Friday, 2020-03-27

*** crobinso has quit IRC00:00
*** david-lyle has joined #kata-dev00:35
*** dklyle has quit IRC00:38
*** EricAdamsZNC has quit IRC00:38
*** EricAdamsZNC has joined #kata-dev00:39
*** gmmaharaj has joined #kata-dev00:45
*** gmmaha has quit IRC00:46
*** gmmaharaj is now known as gmmaha00:46
*** dklyle_ has joined #kata-dev01:03
*** david-lyle has quit IRC01:06
*** gmmaha has quit IRC01:07
*** gmmaha has joined #kata-dev01:09
*** jugs has quit IRC05:50
*** sameo_ has joined #kata-dev05:51
*** jugs has joined #kata-dev06:12
*** errordeveloper has joined #kata-dev06:29
*** errordeveloper has quit IRC06:33
*** dklyle_ has quit IRC06:53
*** sgarzare has joined #kata-dev08:16
*** jodh has joined #kata-dev08:17
*** gwhaley has joined #kata-dev08:58
*** davidgiluk has joined #kata-dev09:04
kata-irc-bot<james.o.hunt> @fupan - Hi - I'm looking at ttrpc and have just updated `protobuf-codegen` but this seems to have broken `protoc` with ttrpc which seems to be generating invalid calls to `protobuf::reflect::message::MessageDescriptor::new_pb_name::<T>` . Have you seen that?09:10
*** errordeveloper has joined #kata-dev10:15
*** errordeveloper has quit IRC10:18
*** errordeveloper has joined #kata-dev10:20
*** davidgiluk has quit IRC10:26
*** davidgiluk has joined #kata-dev10:38
*** davidgiluk has quit IRC10:39
*** davidgiluk has joined #kata-dev10:50
*** kata-irc-bot has quit IRC10:57
*** kata-irc-bot has joined #kata-dev10:57
*** gwhaley has quit IRC11:11
*** gwhaley has joined #kata-dev11:13
*** gwhaley has quit IRC12:00
*** davidgiluk has quit IRC12:21
*** devimc has joined #kata-dev12:52
*** openstack has joined #kata-dev13:02
*** ChanServ sets mode: +o openstack13:02
*** gwhaley has joined #kata-dev13:10
devimc@crobinso https://github.com/kata-containers/runtime/pull/768#issuecomment-44291400813:12
fidenciodevimc: taking advantage you're around, have you seen my messages from Yesterday?13:15
devimcfidencio: sorry, nop13:15
fidenciowhile trying to check whether dwalsh's patches for SELinux work, I've found out something quite weird. Seems that s.config.HypervisorConfig (from sandbox) and q.config (from qemu) are totally different pointers13:15
fidenciomaking the ProcessLabel not be passed, never ever, down to qemu13:16
devimcuhmm that's weird13:16
fidenciodevimc: isn't it?13:17
devimcfidencio: let me check dwalsh's patches13:18
fidenciodevimc: in order to test the patches I had to hack the code a little bit to expicitly pass the processLabel down as a string to startSandbox()13:19
fidenciowhich, at least, unblocked us to actually find some issues with the policy we have for Fedora13:19
devimcfidencio: I think you're right because q.config is not a pointer13:21
fidenciodevimc: so, first thing to do, is make hypervisor.config a pointer13:21
fidenciodevimc: and then store ir properly13:21
fidenciodevimc: now, should it be a pointer?13:21
devimcfidencio: I think so13:26
devimchttps://github.com/kata-containers/runtime/blob/master/virtcontainers/qemu.go#L23913:26
devimcfidencio: yes, hypervisor should have a pointer to the sandbox.HypervisorConfig13:28
errordeveloperhi13:33
errordeveloperso I asked earlier about firecracker, see https://github.com/kata-containers/runtime/issues/256413:34
errordeveloperbut I also have tried to replace the kernel for qemu, and had no luck with that13:34
devimcerrordeveloper: custom kernel?13:35
errordeveloperyeah13:36
errordeveloperI just tried to introduce a bzImage I happen to have13:36
errordeveloperfirst it failed with a misterious `failed to create containerd task: write /sys/class/scsi_host/host1/scan: invalid argument: unknown`13:37
errordeveloperI gathered that actually come13:37
errordeveloper...actually coms13:37
errordeveloper(sorry, typing to fast, so must used to slack these days)13:37
devimcerrordeveloper: I recommend you to use our kernel fragments13:38
devimchttps://github.com/kata-containers/packaging/tree/master/kernel/configs/fragments13:38
errordeveloperI gathered that error comes from the VM, and the scsi driver is actually missing13:38
devimcthese configs are the minimum required to run kata containers13:39
errordeveloperdevimc: I see, I'd use that, but the purpose of my experiment is to enable testing of different kernels with Kata, possibly even Ubuntu and RedHat kernels13:39
devimcerrordeveloper: so, you plan is to use distros's kernels ?13:39
errordeveloperso I am trying to figure out if I can use a pre-built kernel and modules13:39
errordeveloperyeah, I'd like to be able to use distro kernel13:40
errordeveloperthe use case is basically about testing our software (Cilium), on kubernetes, with different kernel13:40
devimcerrordeveloper: take a look to @fidencio and @crobinso's work13:40
devimcthey use fedora's kernel13:41
errordeveloperI want to run Kubernetes nodes inside pods that run on kata, and set kernel version13:41
errordeveloperdevimc: any more specific pointers?13:41
fidencioerrordeveloper: what exactly are you trying to achieve?13:42
fidenciosorry, I was not exactly followin13:42
fidencio*following13:42
devimcfidencio: he wants to use the ubuntu kernel / modules to run kata, so I think he will need dracut/systemd to load the modules13:43
errordeveloperyeah13:43
fidenciodevimc: aha, that's quite similar to what we have done for Fedora, I'd say13:44
fidencioerrordeveloper: ^13:44
devimcfidencio: yeah13:44
fidencioerrordeveloper: would be okay if I point you to our osbuilder scripts?13:44
errordeveloperfidencio: is there a repo I can look at?13:44
errordeveloperanything will do really13:44
fidencioerrordeveloper: https://src.fedoraproject.org/rpms/kata-osbuilder/tree/master13:45
fidencioerrordeveloper: mostly, take a look at fedora-kata-osbuilder.sh13:45
errordeveloperso do you take fedora rootfs and kernel, make an image and let kata use that instead of clearlinux one?13:47
devimcerrordeveloper: basically the initrd/image has the kernel modules and systemd loads them13:47
errordeveloperok, so few bits I'm still no clear about, is it up to the user to select either initrd or image? what is the difference?13:47
devimcerrordeveloper: clearlinux?13:47
errordeveloperyeah, that's what I meant13:48
fidencioerrordeveloper: yeah, we use initrd13:48
fidencioerrordeveloper: but that's the idea13:48
fidencioerrordeveloper: it's up to the user to choose initrd vs image13:48
fidencioerrordeveloper: devimc has some data (as he pointed to Cole) about which one is faster / has less memory footprint / whatnot13:49
errordeveloperah there alpine-based initrd, and clearlinux-base image13:49
errordeveloperok, gottcha13:49
errordeveloperI wonder if anyone explored using docker images for this stuff?13:50
errordeveloperat least as a distribution method.. it would be quite convenient13:50
errordeveloper(just an idea)13:51
errordeveloperor a least a dockerize image/kernel build infra would be handy also...13:53
gwhaleythe osbuilder can build inside docker images - you set USE_DOCKER or similar iirc - it's in the docs....13:59
gwhaleyand v.soon I will be looking at making a custom build script in a dockerfile - but, custom build scripts will I think be just that - they are by nature specific to the modifications you want to make, so will be non-generic... but, might provide a useful base to build upon.14:00
errordevelopergwhaley: I see, I'll have a look at osbuilder, thanks!14:02
gwhaleywhilst here then - errordeveloper - did https://github.com/kata-containers/runtime/issues/2564 still need looking into? I do suspect we should check if ConfigPath is being picked up by kata-runtime shimv2....14:03
gwhaleyerrordeveloper: hmm, it might be that USE_DOCKER only works for osbuilder making rootfs images, and is not available for kernel builds under the packaging repo - sorry, you'll have to wait until I write my dockerfile (or.... volunteer to write one for me ;-) )... I'm hoping to be working on that next week.14:06
kata-irc-bot<dwalsh> So we just got kata-containers using qemu to run with SELinux protections in enforcing mode...  Thanks to @fidencio Creating a new release for containers-selinux and will fix patch for kata today or Monday.14:45
kata-irc-bot<fidencio> \o/14:46
*** dklyle has joined #kata-dev14:57
gwhaleyyay!15:02
*** sameo_ has quit IRC15:20
kata-irc-bot<fidencio> @julio.montes what's the concept of old / new Store for sandboxes?15:31
*** crobinso has joined #kata-dev15:35
devimc@fidencio it's just the way sandbox's state and configuration are saved15:40
devimcin theory, new store was added to support live migration15:40
devimc@fidencio btw I don't use slack, so I don't receive the notifications15:42
devimc:D15:42
fidenciodevimc: we can use IRC :-)15:43
fidenciodevimc: I'm even more comfy here15:43
kata-irc-bot<graham.whaley> we have an irc<->slack bot - so mostly either works - apart from some folks won't see old messages on irc when they log in each day :slightly_smiling_face:15:44
kata-irc-botAction: graham.whaley sits on both, just because....15:44
kata-irc-bot<fidencio> I'd say it depends a lot to which audience I'm communicating with while asking stuff here. If I'm in the middle of a conversation with OpenShift guys, slack tend to be easier.15:45
kata-irc-bot<fidencio> if I'm in the middle of a conversation with virt guys, IRC tend to be easier15:45
devimcslack is too millennial for me15:49
gwhaleyold skool dood15:52
*** sameo has joined #kata-dev16:23
*** devimc has quit IRC16:23
*** devimc has joined #kata-dev16:23
errordevelopergwhaley: yeah, #2564 is still a thing for sure16:50
gwhaleyerrordeveloper: I posted what kata-deploy puts in the containerd config on the Issue for you to check - to see if that helps or hints at all17:02
gwhaleyah, I see maybe you answered (I am behind on my email.... stuck in calls ;-) )17:02
*** pcaruana has quit IRC17:10
errordevelopergwhaley: btw, `make USE_DOCKER=true rootfs` doesn't work on macOS at the moment17:14
errordeveloperit trips over `readlink -f`, which is easy to fix17:14
errordeveloperbut after that it get into some other teritory, and I'm not so sure...17:15
errordeveloperI guess it would be easier if the the whole script just ran in a linux container, instead of split mode as it seems now17:15
errordeveloperlike `docker run -ti  -v /var/run/docker.sock:/var/run/docker.sock -v `pwd`:/src -w /src ubuntu bash -c 'apt update && apt install make docker.io && make USE_DOCKER=true rootfs'` seems to work here17:23
errordeveloper(well, at least it's busy doing something now)17:23
*** pcaruana has joined #kata-dev17:23
kata-irc-bot<graham.whaley> cc @jose.carlos.venegas.m ^^^ for the osbuilder docker thing ;)17:48
*** sgarzare has quit IRC17:49
*** gwhaley has quit IRC18:02
*** jodh has quit IRC18:02
*** crobinso has quit IRC19:15
*** jugs1 has joined #kata-dev19:45
*** kgz has quit IRC19:45
*** jugs has quit IRC19:45
*** kgz has joined #kata-dev19:47
*** devimc has quit IRC21:57
*** sameo has quit IRC22:47
*** sameo has joined #kata-dev22:47
*** errordeveloper has quit IRC23:02

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