Wednesday, 2019-06-12

« Tuesday, 2019-06-11 Index Thursday, 2019-06-13 »
*** igordc has quit IRC01:28
*** tmhoang has quit IRC02:04
*** sameo has joined #kata-general04:43
*** igordc has joined #kata-general05:58
*** kata-irc-bot2 has quit IRC06:51
*** kata-irc-bot has joined #kata-general06:51
*** sameo has quit IRC07:03
*** sameo_ has joined #kata-general07:03
*** tmhoang has joined #kata-general07:10
*** gwhaley has joined #kata-general08:05
*** gwhaley has joined #kata-general08:05
*** igordc has quit IRC08:17
*** sameo_ has quit IRC09:46
*** gwhaley has quit IRC10:57
kata-irc-bot<tarekamalou> i used runtimeClass11:09
kata-irc-bot<tarekamalou>11:13
kata-irc-bot<tarekamalou> when i describe the pod i get this11:15
kata-irc-bot<tarekamalou>11:15
kata-irc-bot<tarekamalou> this is my yaml file: apiVersion:apps/v1 kind: Deployment metadata:   name: webapp spec:   selector:     matchLabels:       app: webapp   replicas: 2   template:     metadata:       labels:         app: webapp     spec:       runtimeClassName: kata-qemu       containers:       - name: webapp         image: richardchesterwood/k8s-fleetman-webapp-angular:release0-511:19
kata-irc-bot<tarekamalou> when i run kubectl describe po kata-deploy i get this11:24
kata-irc-bot<taimoorbhatti> @tarekamalou are you using the correct annotations?11:34
kata-irc-bot<taimoorbhatti> This is my `yaml` file: ``` apiVersion: v1 kind: Pod metadata:     annotations:         com.github.containers.virtcontainers.KernelPath: "/usr/share/kata-containers/vmlinuz-4.19.31-40"     name: kata-example spec:   runtimeClassName: kata-qemu   # restartPolicy: Never    containers:   - name: nginx-container     image: nginx ```11:36
kata-irc-bot<tarekamalou> @taimoorbhatti i'll try it and tell you11:38
kata-irc-bot<taimoorbhatti> you can probably skip the `annotations:` thing... I was testing with a custom kernel11:39
kata-irc-bot<tarekamalou> let's wait for it11:44
*** sameo_ has joined #kata-general11:59
kata-irc-bot<tarekamalou> @taimoorbhatti   how to check if it's a normal container or a kata one ?12:01
kata-irc-bot<taimoorbhatti> `ps aux | grep qemu` will check if a `qemu` process is running12:02
kata-irc-bot<tarekamalou> root      36110  0.0  0.0 112708   976 pts/0    S+   13:02   0:00 grep --color=auto qemu12:02
kata-irc-bot<tarekamalou> this is the result12:03
kata-irc-bot<taimoorbhatti> doesn't look very promising :slightly_smiling_face:12:03
kata-irc-bot<tarekamalou> so whta should i do12:04
kata-irc-bot<taimoorbhatti> can you put the whole output of `kubectl describe` here?12:04
kata-irc-bot<tarekamalou> describe the pod nginx or kata deploy ?12:05
kata-irc-bot<taimoorbhatti> `nginx` maybe12:05
kata-irc-bot<taimoorbhatti> I'm also new to kata... so I'm probably not the best help out there12:06
kata-irc-bot<tarekamalou> Name:               kata-example Namespace:          default Priority:           0 PriorityClassName:  <none> Node:               node3/192.168.1.152 Start Time:         Wed, 12 Jun 2019 12:43:05 +0100 Labels:             <none> Annotations:        kubectl.kubernetes.io/last-applied-configuration:12:06
kata-irc-bot{"apiVersion":"v1","kind":"Pod","metadata":{"annotations":{},"name":"kata-example","namespace":"default"},"spec":{"containers":[{"image":"... Status:             Running IP:                 10.244.2.22 Containers:   nginx-container:     Container ID:   cri-o://044e2587b923511351f6e02fd493f80d55be73a3676d07ec398f43d9810d2e3b     Image:          nginx     Image ID:12:06
kata-irc-botdocker.io/library/nginx@sha256:079aa93463d2566b7a81cbdf856afc6d4d2a6f9100ca3bcbecf24ade92c9a7fe     Port:           <none>     Host Port:      <none>     State:          Running       Started:      Wed, 12 Jun 2019 12:48:52 +0100     Ready:          True     Restart Count:  0     Environment:    <none>     Mounts:       /var/run/secrets/kubernetes.io/serviceaccount from default-token-dn7zz (ro) Conditions:   Type              Status12:06
kata-irc-botInitialized       True   Ready             True   ContainersReady   True   PodScheduled      True Volumes:   default-token-dn7zz:     Type:        Secret (a volume populated by a Secret)     SecretName:  default-token-dn7zz     Optional:    false QoS Class:       BestEffort Node-Selectors:  <none> Tolerations:     node.kubernetes.io/not-ready:NoExecute for 300s                  node.kubernetes.io/unreachable:NoExecute for 300s Events:   Type12:06
kata-irc-bot Reason     Age   From               Message   ----    ------     ----  ----               -------   Normal  Scheduled  23m   default-scheduler  Successfully assigned default/kata-example to node3   Normal  Pulling    22m   kubelet, node3     Pulling image "nginx"   Normal  Pulled     17m   kubelet, node3     Successfully pulled image "nginx"   Normal  Created    17m   kubelet, node3     Created container nginx-container   Normal  Started12:06
kata-irc-bot17m   kubelet, node3     Started container nginx-container12:06
*** gwhaley has joined #kata-general12:10
kata-irc-bot<taimoorbhatti> on `node3`, do you have `kata-runtime` properly installed? (`which kata-runtime`) can you also run: `sudo ctr run --runtime io.containerd.run.kata.v2 -t --rm docker.io/library/ubuntu:16.04 hello bash` to confirm that you _can_ in fact run kata containers on this node properly?12:12
kata-irc-bot<tarekamalou> i used the kata deploy12:12
kata-irc-bot<tarekamalou>12:16
kata-irc-bot<graham.whaley> @tarekamalou Did you apply the runtimeclass kind yaml to bind the kata runtime to the runtimeclass type? https://github.com/kata-containers/packaging/tree/master/kata-deploy/k8s-1.14 ?12:21
kata-irc-bot<graham.whaley> maybe posting a  describe of the kata-deploy pod on that node (is in namespace kube-system) here will help @gmmaharaj @eric.ernst help work out what is not happening12:22
kata-irc-bot<tarekamalou> yeah i did that12:23
kata-irc-bot<tarekamalou> Name:               kata-deploy-jkgpg Namespace:          kube-system Priority:           0 PriorityClassName:  <none> Node:               node3/192.168.1.152 Start Time:         Thu, 06 Jun 2019 11:21:01 +0100 Labels:             controller-revision-hash=775b5865dc                     name=kata-deploy                     pod-template-generation=1 Annotations:        <none> Status:             Running IP:12:24
kata-irc-bot10.244.2.21 Controlled By:      DaemonSet/kata-deploy Containers:   kube-kata:     Container ID:  cri-o://a7baeb3988a6c6a7331d1b04b4837936530a26e2b8ad8057735628a964906ad1     Image:         katadocker/kata-deploy     Image ID:      docker.io/katadocker/kata-deploy@sha256:e9e76236bbf774c3d993e60a5b0d498e5cc2517cbb77450fa32def7b18ac8286     Port:          <none>     Host Port:     <none>     Command:       bash       -c12:24
kata-irc-bot/opt/kata-artifacts/scripts/kata-deploy.sh install     State:          Running       Started:      Wed, 12 Jun 2019 12:12:10 +0100     Last State:     Terminated       Reason:       Error       Exit Code:    255       Started:      Sun, 09 Jun 2019 00:58:57 +0100       Finished:     Wed, 12 Jun 2019 12:10:18 +0100     Ready:          True     Restart Count:  4     Environment:       NODE_NAME:   (v1:spec.nodeName)     Mounts:12:24
kata-irc-bot/etc/containerd/ from containerd-conf (rw)       /etc/crio/ from crio-conf (rw)       /opt/kata/ from kata-artifacts (rw)       /run/systemd from systemd (rw)       /usr/local/bin/ from local-bin (rw)       /var/run/dbus from dbus (rw)       /var/run/secrets/kubernetes.io/serviceaccount from kata-label-node-token-vvgbk (ro) Conditions:   Type              Status   Initialized       True   Ready             True   ContainersReady   True12:24
kata-irc-botPodScheduled      True Volumes:   crio-conf:     Type:          HostPath (bare host directory volume)     Path:          /etc/crio/     HostPathType:   containerd-conf:     Type:          HostPath (bare host directory volume)     Path:          /etc/containerd/     HostPathType:   kata-artifacts:     Type:          HostPath (bare host directory volume)     Path:          /opt/kata/     HostPathType:  DirectoryOrCreate   dbus:     Type:12:24
kata-irc-bot HostPath (bare host directory volume)     Path:          /var/run/dbus     HostPathType:   systemd:     Type:          HostPath (bare host directory volume)     Path:          /run/systemd     HostPathType:   local-bin:     Type:          HostPath (bare host directory volume)     Path:          /usr/local/bin/     HostPathType:   kata-label-node-token-vvgbk:     Type:        Secret (a volume populated by a Secret)     SecretName:12:24
kata-irc-botkata-label-node-token-vvgbk     Optional:    false QoS Class:       BestEffort Node-Selectors:  <none> Tolerations:     node.kubernetes.io/disk-pressure:NoSchedule                  node.kubernetes.io/memory-pressure:NoSchedule                  node.kubernetes.io/not-ready:NoExecute                  node.kubernetes.io/pid-pressure:NoSchedule                  node.kubernetes.io/unreachable:NoExecute12:24
kata-irc-botnode.kubernetes.io/unschedulable:NoSchedule Events:          <none>12:24
kata-irc-bot<graham.whaley> this bit leaps out at me:12:28
kata-irc-bot<graham.whaley> ```Last State:     Terminated      Reason:       Error      Exit Code:    25512:28
kata-irc-bot<graham.whaley> we probably need some input on how to debug kata-deploy fails (and, yeah, I suspect longer term we can make kata deploy better at reporting issues, but I think it is fairly hard from a daemonset)12:29
kata-irc-bot<tarekamalou> yeah i think so12:30
kata-irc-bot<tarekamalou> i don't know what to do now :S12:30
kata-irc-bot<taimoorbhatti> again, I'm the worst guy on the internet atm to help you debugging :slightly_smiling_face: but my understanding was that the binary files were picked up from the host: https://github.com/kata-containers/packaging/blob/master/kata-deploy/kata-deploy.yaml#L33-L6512:43
kata-irc-bot<taimoorbhatti> so if Tarek doesn't have the `kata-runtime` installed at `/opt/kata`, Kubernetes won't pick it up... or am i totally wrong here??12:44
kata-irc-bot<graham.whaley> correct @taimoorbhatti - when you run `kata-deploy`, it sets up a number of items on all the nodes, including copying the kata binaries and config files into `/opt/kata/*` on the nodes. So, when it works, you should see `kata-runtime` for instance in `/opt/kata/bin` on every node (that was eligable for kata-runtime, which I think is all of them by default). It looks to me like `kata-deploy` did not run/complete. Now we have to12:48
kata-irc-botwork out why. best we wait for the folks on the West coast to awake to help us with that I think. I wonder if @krsna1729 might have input as well.12:48
kata-irc-bot<graham.whaley> I could tell you how to locate the kata-deploy pod on the node and then `exec` into it and hand-run the kata-deploy script and see what it does - but, that is a little in-depth and long winded - and I'd rather we worked out or worked on a better way for kata-deploy to expose issues if we can ;) Out of interest then, the script kata-deploy runs is at: (/me goes to find link...)12:49
kata-irc-bot<graham.whaley> https://github.com/kata-containers/packaging/blob/master/kata-deploy/scripts/kata-deploy.sh12:50
*** CeeMac_ has joined #kata-general13:01
*** CeeMac_ has quit IRC13:02
kata-irc-bot<eric.ernst> What’s your CRI?13:02
kata-irc-bot<tarekamalou> CRI-O13:18
kata-irc-bot<eric.ernst> Can you open an issue with all the details?13:23
kata-irc-bot<eric.ernst> Incl k8s/crio versions?13:23
kata-irc-bot<tarekamalou> what shoud i run ?13:26
kata-irc-bot<tarekamalou> as commande13:26
kata-irc-bot<tarekamalou> crio version 1.11.13-1.rhaos3.11.gitfb88a9c.el713:28
*** igordc has joined #kata-general14:26
kata-irc-bot<niteshkonkar007> I just ran a kubeadm 1.14.2 cluster with crio+runtimeclass but on ppc64le. However I did not use kata-deploy. Let me know if I can help u in anyway @tarekamalou14:45
kata-irc-bot<niteshkonkar007> I just ran a kubeadm 1.14.2 cluster with crio+runtimeclass but on ppc64le. However I did not use kata-deploy. Let me know if I can help u in anyway @tarekamalou15:01
*** tmhoang has quit IRC15:47
*** lcastell has joined #kata-general16:01
kata-irc-bot<tarekamalou> @niteshkonkar007 idk maybe i don't know how to install the cluster correctly :S16:01
*** sameo_ has quit IRC16:02
kata-irc-bot<niteshkonkar007> @tarekamalou: Thats fine. You want a kubernetes cluster with cri-o or containerd or any one of the two CRI's is ok?16:04
kata-irc-bot<tarekamalou> it doesn't metter for me i just need it to be deployed16:30
kata-irc-bot<tarekamalou> @niteshkonkar007 sorry for my late reply16:30
kata-irc-bot<tarekamalou> it's my graduated project and i'm struggling :S16:31
kata-irc-bot<niteshkonkar007> Okay. Lets get a kubeadm cluster deployed first. https://kubernetes.io/docs/setup/production-environment/tools/kubeadm/install-kubeadm/#installing-kubeadm-kubelet-and-kubectl16:34
kata-irc-bot<verytired1> fyi, we received a request from the trademark lawyers who handle the kata marks to update the logo that's used on github to the one that includes the name as well. i'm planning to upload the version that we've previously created that meets those parameters. this is going to help us defend the filings. let me know if you have any questions16:56
*** gwhaley has quit IRC17:00
kata-irc-bot<eric.ernst> Seems pretty non controversial. Thanks for the heads up.17:04
kata-irc-bot<salvador.fuentes> I think I'll need to also update the image on https://github.com/katacontainersbot, right?17:05
*** sameo_ has joined #kata-general17:05
kata-irc-bot<verytired1> @salvador.fuentes you can if you'd like, but the critical thing was getting the image+name in public use alongside the code in some way, so the update I just made covers that17:08
kata-irc-bot<salvador.fuentes> ohh ok, got it, thanks @verytired117:09
*** lcastell has quit IRC18:06
*** lcastell has joined #kata-general18:19
*** lcastell has quit IRC18:31
*** tmhoang has joined #kata-general18:40
*** igordc has quit IRC18:43
*** lcastell has joined #kata-general19:14
*** sameo_ has quit IRC19:48
*** lcastell has quit IRC20:39
*** lcastell has joined #kata-general21:07
*** lcastell has quit IRC21:22
*** CeeMac has quit IRC21:57
« Tuesday, 2019-06-11 Index Thursday, 2019-06-13 »

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