Monday, 2019-04-01

*** irclogbot_0 has quit IRC02:19
*** lpetrut has joined #kata-dev03:50
*** lpetrut has quit IRC04:19
*** sameo has joined #kata-dev05:02
*** sameo has quit IRC06:49
*** tmhoang has joined #kata-dev06:49
*** sgarzare has joined #kata-dev06:56
*** lpetrut has joined #kata-dev06:57
*** jodh has joined #kata-dev07:30
*** sameo has joined #kata-dev07:36
*** davidgiluk has joined #kata-dev08:39
*** devimc has joined #kata-dev12:58
*** davidgiluk has quit IRC13:12
*** irclogbot_1 has joined #kata-dev13:25
*** davidgiluk has joined #kata-dev13:30
*** fuentess has joined #kata-dev13:50
kata-irc-bot<teawater> Got “Jenkins is going to shut down” when I open http://jenkins.katacontainers.io.  Is it going to reboot?14:11
kata-irc-bot<jose.carlos.venegas.m> @gmmaharaj let me take a look14:42
kata-irc-bot<jose.carlos.venegas.m> @gmmaharaj we have the fedora 29 packages successfully created for it14:46
kata-irc-bot<jose.carlos.venegas.m> what package repository are you pointing to ?14:46
*** sameo has quit IRC14:52
*** lpetrut has quit IRC15:04
*** tmhoang has quit IRC16:19
*** sgarzare has quit IRC16:47
*** davidgiluk has quit IRC16:54
*** jodh has quit IRC17:02
*** sameo has joined #kata-dev17:32
kata-irc-bot<eric.ernst> In reviewing pod annotations, I'm thinking it'd be useful to include kernel params on a per pod basis.17:39
kata-irc-bot<eric.ernst> I'm kind of surprised this isn't an option today; am I missing anything?  Today kernel params are *just* set in the toml (so, at a node granularity)?  @bergwolf @samuel.ortiz @manohar.r.castelino @archana.m.shinde ?17:39
kata-irc-bot<samuel.ortiz> @eric.ernst There has not been a use case for this. Yet.17:40
kata-irc-bot<eric.ernst> We have a potential user who was asking about it.18:25
kata-irc-bot<eric.ernst> For me, it could make sense?  Example: ```The application may need a specific kernel parameter value, e.g. ElasticSearch need /proc/sys/vm/max_map_count to be 262144, how can we set it for kata VM?```18:26
kata-irc-bot<archana.m.shinde> @eric.ernst that is more of a sysctl value18:29
kata-irc-bot<archana.m.shinde> I have added a doc that addresses spec that18:29
kata-irc-bot<archana.m.shinde> https://github.com/kata-containers/documentation/blob/master/how-to/how-to-use-sysctls-with-kata.md18:29
kata-irc-bot<archana.m.shinde> kind of a recipe for Kata, by having those set in a privileged container18:31
kata-irc-bot<archana.m.shinde> so that it affects only that guest/container rather than other containers which would not be possible with regular containers18:31
kata-irc-bot<eric.ernst> Nice link, @archana.m.shinde - agreed.18:32
kata-irc-bot<eric.ernst> Trying to see where this sits for forbidden/unsafe/safe list.18:32
kata-irc-bot<eric.ernst> or if it is namespaced18:33
*** igordc has joined #kata-dev18:35
kata-irc-bot<archana.m.shinde> the one that you mentioned `/proc/sys/vm/max_map_count` is not namespaced @eric.ernst18:36
kata-irc-bot<eric.ernst> Yeah, I was hoping that maybe this changed, but not seeing it.18:36
kata-irc-bot<eric.ernst> Thinking, though - wouldn't this be needed on the host?18:37
kata-irc-botAction: eric.ernst is confused18:38
kata-irc-bot<eric.ernst> @manohar.r.castelino ^18:41
*** devimc has quit IRC19:58
*** devimc has joined #kata-dev19:59
kata-irc-bot<manohar.r.castelino> @archana.m.shinde check nproc that is normally accurate20:07
kata-irc-bot<manohar.r.castelino> @eric.ernst do you see case where user chosen kernel params can cause security issues20:08
kata-irc-bot<eric.ernst> @xwlpt ping?20:08
kata-irc-bot<manohar.r.castelino> @eric.ernst we do not sanitize those params today20:08
kata-irc-bot<eric.ernst> I suppose it would open things.20:09
kata-irc-bot<archana.m.shinde> @manohar.r.castelino Didnt follow the nproc thing20:10
kata-irc-bot<manohar.r.castelino> @archana.m.shinde ignore that I did not read the message properly20:10
kata-irc-bot<eric.ernst> they could write it with --priv, which also isn't ideal, but at least they know what they're getting into...20:11
kata-irc-bot<eric.ernst> Or just set it by default.20:11
kata-irc-bot<manohar.r.castelino> @gabrielle.n.beyer on the kata podman work can you check the following even when not running rootless20:12
kata-irc-bot<manohar.r.castelino> create files within the container20:12
kata-irc-bot<manohar.r.castelino> check what the uid and gid end up being on the host side file system20:12
*** jugs has quit IRC20:45
*** jugs has joined #kata-dev20:46
kata-irc-bot<xwlpt> @eric.ernst It is better for user to specify the kernel parameter but not use --priv way. For pod in k8s,  most of the user will not have privileged permission. If they have privileged permission, then they can do almost every at the host.20:47
kata-irc-bot<eric.ernst> Sure, I undertsand.20:48
kata-irc-bot<eric.ernst> What do you think about just setting the kernel parameters via the configuration.toml?20:48
kata-irc-bot<eric.ernst> (this will be a node level setting)20:48
kata-irc-bot<eric.ernst> I'm not sure there's a major draw back (for your specific example)20:48
kata-irc-bot<xwlpt> It is better to make it per pod, so that we can support many kind of different users.20:49
kata-irc-bot<eric.ernst> my concern is that by making that annotation, users could then start expressing more kernel parameters which could be exploitable.21:12
kata-irc-bot<gabrielle.n.beyer> @manohar.r.castelino I may be misunderstanding you, but it looks like both are root, which I guess makes sense since the initial user of the container is root, should I try and make a user within the podman container, and see if it still sets uid/guid to be root in teh storage/overlay on teh host?21:34
kata-irc-bot<gabrielle.n.beyer> [g@podman2 ~]$ sudo ls -lht /var/lib/containers/storage/overlay/06429d218f6236a6c0f18a08445ba2052e1c6cfd66a4d41d237ced03f214e40e/diff/root total 4.0K -rw-r--r-- 1 root root 11 Apr  1 21:27 testfile21:35
*** eernst has joined #kata-dev22:14
*** eernst has quit IRC22:18
*** devimc has quit IRC22:48
*** sameo has quit IRC22:48
*** fuentess has quit IRC23:05
kata-irc-bot<gmmaharaj> Was using the automatic scripts.. didn't choose the repository by hand.23:26
kata-irc-bot<gmmaharaj> Not sure why it was failing..23:26
kata-irc-bot<gmmaharaj> Should I try again @jose.carlos.venegas.m?23:26
kata-irc-bot<gmmaharaj> Sorry was in a day long meeting.. hence no earlier reply..23:26
*** auk has joined #kata-dev23:30
*** auk has quit IRC23:52
*** kata-irc-bot has quit IRC23:53
*** kata-irc-bot has joined #kata-dev23:54

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