Friday, 2019-02-08

*** lcastell has quit IRC00:38
*** tmhoang has joined #kata-general07:49
*** gwhaley has joined #kata-general09:30
*** EricAdamsZNC has quit IRC09:56
*** EricAdamsZNC has joined #kata-general10:00
*** eguan has quit IRC11:28
*** eguan has joined #kata-general11:30
*** gwhaley has quit IRC12:01
*** gwhaley has joined #kata-general13:09
*** lpetrut has joined #kata-general13:29
*** sameo has joined #kata-general14:00
kata-irc-bot1<tuan.hoang1> Hi, on system without systemd (like Alpine), what is the reason behind using kata-agent as init instead of using distro's init, and then start kata-agent (as a server/unit) like it was done in systemd-based system ?15:10
kata-irc-bot1<tuan.hoang1> I have not made it there yet, but I think I could just call Alpine's init, and then start a service (/etc/init.d/kata-agent for example) to start kata-agent.15:11
kata-irc-bot1<tuan.hoang1> probably inject a line in Alpine's init to add kata-agent service to rc- boot level (# chroot $ROOTFS_DIR rc-updates add kata-agent)15:12
kata-irc-bot1<tuan.hoang1> if there's no objection, I would like to send a PR sooner or later15:12
kata-irc-bot1<graham.whaley> @tuan.hoang1 I think the Hyper folks have more experience with the initrd stuff, so maybe @xu might know? Also @julio.montes has been in this area I think. My presumption is we place kata as init as, well, if you are just going to use alpine init to call kata init, you may as well skip the alpine init....**unless** there is something else you need alpine (busybox?) init to do as well... In which case, a PR to make that an15:19
kata-irc-bot1option of the build I think would be welcome (but, we'd still have to discuss which would be default,  and I think as generally there is nothing else for alpine init to do for kata, we would probalby choose kata as init ?)15:19
kata-irc-bot1<tuan.hoang1> I'm using image btw, not initrd15:19
kata-irc-bot1<tuan.hoang1> understood15:19
kata-irc-bot1<tuan.hoang1> since I'm gradually moving from ubuntu to alpine image, just guessing it might be handy to have alpine's init (i.e. adding ssh service to the VM so I can ssh into it).15:23
kata-irc-bot1<graham.whaley> Right, that would be a good example of a use case - but, that specific case we say is only for debug - because it is a security hole ;) So, the option in the package builder to add alpine init as the init, and instructions of then how to add the debug console to that setup, would be v.nice ;)15:27
*** lpetrut has quit IRC15:29
*** lpetrut has joined #kata-general15:30
kata-irc-bot1<tuan.hoang1> I'm looking forward to the day kata arrives in mainstream distros' repository and I could add kata to Alpine repo :slightly_smiling_face:15:31
kata-irc-bot1<daniel.gehberger> Hi! I wanted to try kata with Firecracker (without Docker). I downloaded the static tar and wanted to do run like I would with qemu, having a decompressed alpine image under ./rootfs, but it fails:  xx:~/container$ sudo /opt/kata/bin/kata-fc spec xx:~/container$ sudo /opt/kata/bin/kata-fc run test rpc error: code = Unknown desc = rootfs (/run/kata-containers/shared/containers/test/rootfs) does not exist xx:~/container$ sudo15:40
kata-irc-bot1/opt/kata/bin/kata-qemu run test / #  I guess it is related to the devicemapper requirement. Do you maybe have some example how to do this? Thanks!15:40
kata-irc-bot1<graham.whaley> @daniel.gehberger - do you have devicemapper enabled? fc needs it to run with kata. beyond that, @eric.ernst and @manohar.r.castelino may be able to answer15:43
*** lpetrut has quit IRC15:51
kata-irc-bot1<daniel.gehberger> I am not sure what you mean by "enabled" without using Docker. My guess is that I have to create a drive and mount it where it misses the rootfs...?16:06
*** tmhoang has quit IRC16:46
*** sameo has quit IRC17:08
*** gwhaley has quit IRC18:00
*** stackedsax has quit IRC18:19
*** sameo has joined #kata-general20:15
kata-irc-bot1<raravena80> I suppose you either need docker or k8s20:37
*** sameo has quit IRC22:30

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