Thursday, 2020-12-03

*** georgk has quit IRC02:16
*** georgk has joined #kata-dev02:17
*** sameo has quit IRC06:38
*** snir has joined #kata-dev07:04
*** dklyle has quit IRC07:31
*** fgiudici has joined #kata-dev07:43
*** sgarzare has joined #kata-dev08:10
*** sameo has joined #kata-dev08:20
*** jodh has joined #kata-dev08:40
*** amorenoz has quit IRC08:53
*** amorenoz has joined #kata-dev08:53
*** davidgiluk has joined #kata-dev09:07
*** ailan has joined #kata-dev11:43
*** devimc has joined #kata-dev13:18
*** mugsie has quit IRC13:32
*** crobinso has joined #kata-dev13:34
kata-irc-bot<christophe> Funny error message of the day: ```# podman run -it --rm --runtime kata --memory 256 fedora bash                                                      Error: container create failed (no logs from conmon): EOF``` From what I can tell, 256 is interpreted as 256 bytes. That seems moderately useful.13:38
kata-irc-bot<christophe> For what it's worth, related to discussions we had elsewhere, `dnf install` seems unstable with 256M containers. ```[root@6263dc928ca8 /]# dnf install -y emacs  Fedora 33 openh264 (From Cisco) - x86_64        923  B/s | 2.5 kB     00:02     Fedora Modular 33 - x86_64                      737 kB/s | 3.3 MB     00:04     Fedora Modular 33 - x86_64 - Updates            626 kB/s | 2.9 MB     00:04     Fedora 33 - x86_64 - Updates13:40
kata-irc-bot          893 kB/s |  16 MB     00:18     Killed [root@6263dc928ca8 /]# echo $? 137``` That is by setting the `default_memory` to 256. If you set the memory with the command-line, then instead you get what looks like a solid hang. I'll wait a little longer to confirm.13:40
kata-irc-bot<christophe> @eric.ernst I know you have been looking at minimum memory sizes. Can I ask what image you were trying to run?13:40
kata-irc-bot<durand.didier> Are you getting this with Kata v1 or v2 as  I have a ticket open related to --runtime kata --rm with v2… It fails right away.13:43
kata-irc-bot<wmoschet> Hi folks! can I have permission to set labels on github.com/kata-containers/kata-containers ?13:59
*** fuentess has joined #kata-dev14:03
*** sameo has quit IRC14:54
*** dklyle has joined #kata-dev14:58
*** pcaruana has quit IRC15:04
*** pcaruana has joined #kata-dev15:05
devimc@wmoschet done15:23
*** devimc has quit IRC15:30
*** devimc has joined #kata-dev15:31
kata-irc-bot<wmoschet> devimc: gracias!15:42
*** pcaruana has quit IRC16:16
*** pcaruana has joined #kata-dev16:21
*** dklyle has quit IRC16:25
*** dklyle has joined #kata-dev16:25
*** sameo has joined #kata-dev16:46
*** sgarzare has quit IRC17:12
kata-irc-bot<christophe> Could someone with the correct authority rename the `runtime-private` to `runtime-CVE-2020-27151` and make it public? I asked for CVE update and published the KCSA (PR here: https://github.com/kata-containers/community/pull/192). Thanks17:23
kata-irc-bot<christophe> @archana.m.shinde ^ (Please review, this is my first KCSA :) )17:25
*** crobinso has quit IRC17:35
*** pcaruana has quit IRC17:45
*** jodh has quit IRC18:04
*** fgiudici has quit IRC18:30
kata-irc-bot<wmoschet> I'm working to now get kata 2.x tested on openshift CI. It will speed up the process and make my life easier if I could have a remote branch on kata-containers/kata-containers repo. That branch will be used to develop and test CI scripts on CI itself. Is it possible?18:45
devimc@wmoschet indeed19:59
devimcyou can name it openshift19:59
kata-irc-bot<wmoschet> devimc: cool. so I will create it. Thanks!20:00
devimc@wmoschet np20:00
*** ailan has quit IRC20:05
*** davidgiluk has quit IRC20:12
*** crobinso has joined #kata-dev20:33
*** devimc has quit IRC22:01
*** sameo has quit IRC22:22
*** fuentess has quit IRC23:39
*** fuentess1 has joined #kata-dev23:39

Generated by irclog2html.py 2.17.2 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!