Friday, 2020-04-03

*** sameo has joined #kata-general05:00
*** igordc has quit IRC06:21
*** sgarzare has joined #kata-general07:21
*** gwhaley has joined #kata-general08:07
*** devimc has joined #kata-general13:00
*** pvdp66556 has quit IRC13:56
*** devimc has quit IRC14:11
*** devimc has joined #kata-general14:12
*** kata-irc-bot1 has quit IRC15:15
*** kata-irc-bot has joined #kata-general15:18
*** igordc has joined #kata-general15:32
*** sgarzare has quit IRC16:48
*** devimc has quit IRC16:49
*** devimc has joined #kata-general16:49
*** gwhaley has quit IRC17:07
kata-irc-bot<philip.schmidt> Hey all, is there a way to nsenter into a kata container if a container is priviliged? I notice https://github.com/kata-containers/runtime/blob/master/virtcontainers/pkg/nsenter/nsenter.go but wasnt sure if will be any different to nsenter which doesnt properly nsenter into the actual kata container...19:24
kata-irc-bot<philip.schmidt> so it looks like `kata-runtime exec` is my solution. but it fails saying that the container ID is not found even though it shows up in `kata-runtime list`20:21
kata-irc-bot<eric.ernst> What exactly are you hoping to do?20:31
kata-irc-bot<eric.ernst> What kind of runtime are you using above Kata?20:31
kata-irc-bot<eric.ernst> You can kubetl exec, or docker exec20:31
kata-irc-bot<philip.schmidt> the runtime is kube but is there an alternative to using `kube exec`? Using `kube exec` will trigger a security alert in production. The goal is to do network monitoring in a kata container by  runnint something like `netstat -tup` in the container and getting results20:42
*** sameo has quit IRC21:01
*** devimc has quit IRC22:02
*** pvdp66556 has joined #kata-general22:23
*** igordc has quit IRC22:36
*** igordc has joined #kata-general22:36

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