Thursday, 2019-04-04

*** igordc has quit IRC00:36
*** auk has joined #kata-dev01:00
*** sameo has joined #kata-dev04:49
*** tmhoang has joined #kata-dev06:45
*** sameo has quit IRC06:46
*** auk has quit IRC06:51
*** sgarzare has joined #kata-dev06:57
*** auk has joined #kata-dev07:01
*** auk has quit IRC07:08
*** dims has quit IRC07:22
*** dims has joined #kata-dev07:24
*** sameo has joined #kata-dev07:28
*** dims has quit IRC07:31
*** davidgiluk has joined #kata-dev08:04
*** gwhaley has joined #kata-dev08:17
*** stefanha has joined #kata-dev08:58
stefanhaDoes anyone hit kata-runtime build errors with "make -j4"?  Non-parallel make works fine for me, but "make -j4" doesn't.08:58
stefanha     BUILD   /home/stefanha/kata/goroot/src/github.com/kata-containers/runtime/kata-runtime08:58
stefanha# github.com/kata-containers/runtime/cli08:59
stefanha./delete.go:30:46: undefined: name08:59
stefanhaHmm...maybe this only happens after "git checkout FOO".  If I rerun "make -j4" it builds successfully from then onwards.09:00
gwhaleyhi stefanha - hmm, not one I've seen before. I'd have to suspect a vendor thing or an auto-gen-in-Makefile race with a dep missing... but, you probably already thought that..09:01
stefanhaIf I figure out how to reproduce it reliably, I'll debug it ;)09:01
kata-irc-bot<calm.wu> https://github.com/kata-containers/documentation/issues/42110:03
stefanhaSummary of calm.wu's link: Running a container with kata + kubernetes (flannel).  Getting connection refused when connecting to port.  Need help troubleshooting networking.10:10
kata-irc-bot<xu> @archana.m.shinde any suggestion?10:11
*** jugs has quit IRC10:45
*** jugs has joined #kata-dev10:45
*** tmhoang_ has joined #kata-dev11:01
*** gwhaley has quit IRC11:02
*** tmhoang has quit IRC11:04
*** tmhoang_ has quit IRC11:05
*** tmhoang_ has joined #kata-dev11:06
*** tmhoang__ has joined #kata-dev11:08
*** tmhoang_ has quit IRC11:12
*** jugs has quit IRC11:27
*** jugs has joined #kata-dev11:27
*** dims has joined #kata-dev12:16
*** gwhaley has joined #kata-dev12:18
*** sgarzare has quit IRC12:25
*** sgarzare has joined #kata-dev12:29
*** tmhoang__ is now known as tmhoang12:33
*** devimc has joined #kata-dev12:59
*** dklyle has quit IRC13:02
kata-irc-bot<calm.wu> ?13:05
kata-irc-bot<graham.whaley> hi @calm.wu - welcome here. A bunch of the developers are in U.S., so will not be online yet - but - the nice thing with slack is they will see your query when they come online... wrt your issue 421 - maybe @eric.ernst @manohar.r.castelino @archana.m.shinde have some thoughts about the 9090 port not being seen. In the meantime, can you check the boot logs of the container and see that it booted OK? Is tomcat maybe a large13:43
kata-irc-botapplication? Maybe you need to try starting it with more memory - kata defaults to 1-2Gb of RAM if it is not told otherwise.13:43
*** altlogbot_2 has quit IRC13:54
*** fuentess has joined #kata-dev14:04
kata-irc-bot<calm.wu> hi @graham.whaley, tomcat listening on port 8080, use command "crictl exec containerid curl 127.0.0.0:8080" return is correct. I use "kubectl apply -f calmwupod.yaml" start a container, can you tell me where the container's bool log is?14:11
kata-irc-bot<graham.whaley> @calm.wu - ah, if exec on 127.0.0.1 gives correct output, yes, that implies pod has booted. maybe 'kubectl logs <podname>' will show you the boot log, and you can check if it completed.14:14
kata-irc-bot<calm.wu> @graham.whaley Log output "unable to allocate file descriptor table - out of memory ....."14:23
kata-irc-bot<calm.wu> @graham.whaley "a fatal error has been detected by the java Runtime Environment"14:26
kata-irc-bot<graham.whaley> right - my first guess is you need to assign more memory to the pod - in your toml file. Start with lots maybe to see if it is the problem. If that boots then you can work out how much you really need later. Or, maybe you can configure tomcat to use less.14:27
*** gwhaley has quit IRC14:30
kata-irc-bot<calm.wu> @graham.whaley In /usr/share/default/kata-containers/configuration.toml, default_memory = 2048, Increase default_memory value?14:33
kata-irc-bot<graham.whaley> you can do that @calm.wu - that will increase the default memory for all kata containers. Or, if you use the kubernetes or docker commands to define how much memory the pod/container needs, then that will be used instead by docker.14:34
kata-irc-bot<graham.whaley> s/docker/kata/ btw ;)14:37
kata-irc-bot<calm.wu> Got it @graham.whaley, in pod yaml, set .spec.containers.resources.requests.memory14:38
kata-irc-bot<graham.whaley> yes, I think that'll be the one @calm.wu14:38
kata-irc-bot<calm.wu> @graham.whaley thank you very much, I'll try14:39
*** gwhaley has joined #kata-dev14:43
*** dklyle has joined #kata-dev15:27
*** sameo has quit IRC15:51
kata-irc-bot<eric.ernst> review help?  https://github.com/pulls?utf8=%E2%9C%93&q=is%3Aopen+is%3Apr+author%3Aegernst+archived%3Afalse++Kata+Containers16:06
*** tmhoang has quit IRC16:17
*** igordc has joined #kata-dev16:33
*** sgarzare has quit IRC16:49
*** gwhaley has quit IRC17:08
*** sameo has joined #kata-dev17:21
kata-irc-bot<raravena80> looks like the SPDX license issue is there.17:23
*** davidgiluk has quit IRC17:55
*** sameo has quit IRC18:28
*** davidgiluk has joined #kata-dev18:41
*** davidgiluk has quit IRC19:20
*** devimc has quit IRC21:40
*** fuentess has quit IRC22:11
*** jugs has quit IRC22:32
*** jugs has joined #kata-dev22:33
*** igordc has quit IRC22:34
*** dklyle has quit IRC23:19
*** auk has joined #kata-dev23:35
*** igordc has joined #kata-dev23:39

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