kata-irc-bot | <arshad.rad> why there isn't any katactl? | 00:28 |
---|---|---|
kata-irc-bot | <raravena80> @arshad.rad I think essentially boils down to having either `docker` for Kata with Docker and having `kubectl`, `crictl`, and `ctr` (containerd) with Kubernetes. Is there a reason why you thing having a `katactl` would be useful? Also, `kata-runtime` has several subcommands. For example `kata-runtime kata-check` and `kata-runtime list` | 01:33 |
kata-irc-bot | <bergwolf> @arshad.rad As I have replied in issue #1135, you need `initrd` to use with vm templating and `kata-runtime factory` subcommand can help create and destroy the template image. | 01:40 |
kata-irc-bot | <arshad.rad> @bergwolf thanks peng! as the default configuration had only "image=" it showed up unknown error but once i tried the source code i could realize "initrd=", maybe you guys need to fix it. | 01:43 |
kata-irc-bot | <bergwolf> I thought we have returned some error message when `initrd` is not set but vm templating is enabled. Were you able to see such error message? | 01:44 |
kata-irc-bot | <arshad.rad> @raravena80 right, i didn't know the kata-runtime subcommands ... i was thinking about first use case about purge vm template snapshot that now i need to use kata-runtime. | 01:45 |
kata-irc-bot | <arshad.rad> @bergwolf error was : docker: Error response from daemon: OCI runtime create failed: Failed to check if grpc server is working: rpc error: code = Unavailable desc = transport is closing: unknown. | 01:45 |
kata-irc-bot | <bergwolf> hmm, let's me check | 01:46 |
kata-irc-bot | <arshad.rad> if you have only "image=" not "initrd" w/ vm template enabled, then you get the above error, as i got | 01:47 |
kata-irc-bot | <arshad.rad> @bergwolf ^^^ | 01:47 |
kata-irc-bot | <bergwolf> @arshad.rad This is what I have when enabling vm templating but only have `image=` ``` $docker run --rm -it --runtime kata busybox docker: Error response from daemon: OCI runtime create failed: Factory option enable_template requires an initrd image: unknown. ``` | 01:52 |
kata-irc-bot | <bergwolf> Are you running the latest kata runtime code? | 01:53 |
kata-irc-bot | <arshad.rad> i just tried again and same @bergwolf | 01:55 |
kata-irc-bot | <arshad.rad> kata-runtime --version kata-runtime : 1.5.0-rc2 commit : 9b9ff2b7e6b795230a5008e0cb6751ec3e2c17e1 OCI specs: 1.0.1-dev | 01:55 |
kata-irc-bot | <arshad.rad> #initrd = "/usr/share/kata-containers/kata-containers-initrd.img" image = "/usr/share/kata-containers/kata-containers.img" enable_template = true | 01:55 |
kata-irc-bot | <arshad.rad> once the image is in place w/o initrd | 01:56 |
kata-irc-bot | <bergwolf> That's weird. ``` [macbeth@runtime]$kata-runtime --version kata-runtime : 1.5.0-rc2 commit : 9b9ff2b7e6b795230a5008e0cb6751ec3e2c17e1 OCI specs: 1.0.1-dev [macbeth@runtime]$grep "initrd =" /etc/kata-containers/configuration.toml #initrd = "/golang/src/github.com/kata-containers/osbuilder/kata-containers-initrd.img" [macbeth@runtime]$grep "image =" /etc/kata-containers/configuration.toml image = | 02:01 |
kata-irc-bot | "/golang/src/github.com/kata-containers/osbuilder/kata-containers.img" [macbeth@runtime]$grep "enable_template =" /etc/kata-containers/configuration.toml enable_template = true [macbeth@runtime]$docker run --rm -it --runtime kata busybox docker: Error response from daemon: OCI runtime create failed: Factory option enable_template requires an initrd image: unknown. ERRO[0000] error waiting for container: context canceled ``` | 02:01 |
kata-irc-bot | <arshad.rad> let me reinstall my kata, maybe because i upgraded it through source code | 02:04 |
kata-irc-bot | <bergwolf> We are running the same version of kata runtime code and the same config, but get different results w.r.t. config option check. I'm out of idea why it happens | 02:05 |
kata-irc-bot | <bergwolf> I'm also building from source | 02:05 |
kata-irc-bot | <bergwolf> btw, the very specific commit that checks `initrd` option for vm template is `0bf29c8207d6e62987f738ffc781a745dc6b9ba3` and it went in after `1.4.0` release. ``` [macbeth@runtime]$git describe 0bf29c8207d6e62987f738ffc781a745dc6b9ba3 1.4.0-34-g0bf29c82 ``` | 02:11 |
kata-irc-bot | <bergwolf> @arshad.rad I guess your docker is still calling some old `kata-runtime` binary even after you installed it from source. | 02:15 |
kata-irc-bot | <bergwolf> Please check your docker config to make sure it calls the new one | 02:15 |
kata-irc-bot | <arshad.rad> @bergwolf thanks, i'll try again from source code later (latest version) I think it was calling the kata-runtime that it installed through: https://github.com/kata-containers/documentation/blob/master/install/ubuntu-installation-guide.md | 02:18 |
kata-irc-bot | <bergwolf> That commit didn't make it to `stable-1.4` so you need to run 1.5-rc(x) to have it. The latest code will work too. | 02:20 |
kata-irc-bot | <arshad.rad> right. the docker was calling the kata-runtime v 1.4.2 | 02:20 |
kata-irc-bot | <arshad.rad> now it shows correct error: | 02:21 |
kata-irc-bot | <arshad.rad> root@ip-10-0-0-97:~/go/src/github.com/kata-containers/runtime# time docker run -d redis 6933f1be11e70440b6ecc9088ac6af28fdf1b518c929fe5cc97f5894dc8ae976 docker: Error response from daemon: OCI runtime create failed: Factory option enable_template requires an initrd image: unknown. | 02:21 |
kata-irc-bot | <arshad.rad> thanks for your help @bergwolf | 02:21 |
kata-irc-bot | <bergwolf> cool | 02:21 |
kata-irc-bot | <bergwolf> np. enjoy playing with kata ;) | 02:21 |
kata-irc-bot | <arshad.rad> the source code put the runtime under /usr/local/bin but the ubuntu package it put at /usr/bin that's why i had two kata runtime | 02:22 |
kata-irc-bot | <bergwolf> yeah, manual installation usually ends up with `/usr/local/bin` but distros prefer `/usr/bin` | 02:23 |
kata-irc-bot | <xu> not “prefer”, it is specified by FHS and maintainers guide. | 02:24 |
kata-irc-bot | <xu> A distro packager should never package stuff in `/usr/local/`, where is the privilege sysadmins. | 02:25 |
kata-irc-bot | <xu> And we should have this issue (template configuration) in FAQ | 02:26 |
kata-irc-bot | <bergwolf> We have the `initrd` requirement documented in the config file: ``` [factory] # VM templating support. Once enabled, new VMs are created from template # using vm cloning. They will share the same initial kernel, initramfs and # agent memory by mapping it readonly. It helps speeding up new container # creation and saves a lot of memory if there are many kata containers running # on the same host. # # When disabled, new VMs are | 02:28 |
kata-irc-bot | created from scratch. # # Note: Requires "initrd=" to be set ("image=" is not supported). # # Default false #enable_template = true ``` | 02:28 |
kata-irc-bot | <xu> Yes, but some github issue should be summary to a FAQ | 02:31 |
kata-irc-bot | <bergwolf> hmmm, it seems we don't have a FAQ doc yet. Maybe it's time to create one? | 02:34 |
kata-irc-bot | <xu> labeled the issue as `FAQ`, and do more later | 02:35 |
kata-irc-bot | <bergwolf> or just for this one, I can put some doc in the `how-to` directory. | 02:36 |
kata-irc-bot | <bergwolf> I saw you have labeled it already. Thanks! | 02:37 |
*** sjas has quit IRC | 02:46 | |
kata-irc-bot | <raravena80> @eric.ernst @graham.whaley @james.o.hunt @mvedovati @salvador.fuentes @samuel.ortiz can you guys join the github actions beta https://github.com/features/actions/ ? basically, my github and @jose.carlos.venegas.m' were added because we had signed up initially, once you sign up for the beta your accounts can be added. I'm not sure who owns katacontainersbot but that user/account needs to sign up too. @eric.ernst | 02:55 |
kata-irc-bot | @jose.carlos.venegas.m you know? | 02:55 |
*** sjas has joined #kata-general | 02:55 | |
*** Bhujay has joined #kata-general | 05:20 | |
*** Bhujay has quit IRC | 05:21 | |
*** Bhujay has joined #kata-general | 05:21 | |
*** Bhujay has quit IRC | 06:07 | |
*** Bhujay has joined #kata-general | 06:07 | |
*** Bhujay has quit IRC | 06:08 | |
*** Bhujay has joined #kata-general | 06:08 | |
*** Bhujay has quit IRC | 06:10 | |
*** Bhujay has joined #kata-general | 06:10 | |
*** Bhujay has quit IRC | 06:11 | |
*** Bhujay has joined #kata-general | 06:11 | |
*** Bhujay has quit IRC | 06:13 | |
*** Bhujay has joined #kata-general | 06:13 | |
*** Bhujay has quit IRC | 06:14 | |
*** Bhujay has joined #kata-general | 06:14 | |
*** Bhujay has quit IRC | 06:16 | |
*** Bhujay has joined #kata-general | 06:16 | |
*** Bhujay has quit IRC | 06:17 | |
*** Bhujay has joined #kata-general | 06:17 | |
*** Bhujay has quit IRC | 06:19 | |
*** Bhujay has joined #kata-general | 06:19 | |
*** Bhujay has quit IRC | 06:20 | |
*** Bhujay has joined #kata-general | 06:20 | |
*** Bhujay has quit IRC | 06:22 | |
*** Bhujay has joined #kata-general | 06:22 | |
*** Bhujay has quit IRC | 06:23 | |
*** Bhujay has joined #kata-general | 06:23 | |
*** Bhujay has quit IRC | 08:13 | |
*** sameo_ has joined #kata-general | 08:30 | |
*** Bhujay has joined #kata-general | 08:56 | |
*** gwhaley has joined #kata-general | 09:38 | |
*** Bhujay has quit IRC | 10:37 | |
*** Bhujay has joined #kata-general | 10:53 | |
*** lpetrut has joined #kata-general | 11:03 | |
*** gwhaley has quit IRC | 12:03 | |
*** Bhujay has quit IRC | 12:34 | |
*** Bhujay has joined #kata-general | 12:35 | |
*** Bhujay has quit IRC | 12:36 | |
*** Bhujay has joined #kata-general | 12:36 | |
*** Bhujay has quit IRC | 12:37 | |
*** Bhujay has joined #kata-general | 12:40 | |
*** Bhujay has quit IRC | 12:42 | |
*** irclogbot_0 has quit IRC | 12:47 | |
kata-irc-bot | <tuan.hoang1> Hello, I'm pretty new to Kata in general. I'm reading osbuilder code and trying to understand how an image is built without the need of a bootloader. | 12:56 |
kata-irc-bot | <tuan.hoang1> https://github.com/kata-containers/osbuilder/blob/master/image-builder/image_builder.sh | 12:56 |
*** irclogbot_0 has joined #kata-general | 12:56 | |
*** gwhaley has joined #kata-general | 13:17 | |
kata-irc-bot | <teawater> @tuan.hoang1 Because qemu(vmm) can load the kernel to the memory. | 13:31 |
kata-irc-bot | <tuan.hoang1> @teawater: afaiu, there are 2 ways to boot: first using kernel + initrd, second using a disk image with bootloader, kernel, initrd installed. | 13:32 |
kata-irc-bot | <tuan.hoang1> so what you mention is prob the first method ? | 13:33 |
*** irclogbot_0 has quit IRC | 13:45 | |
*** irclogbot_0 has joined #kata-general | 13:54 | |
kata-irc-bot | <tuan.hoang1> it seems what kata does is boot with kernel and the disk image, so no need for bootloader | 14:35 |
kata-irc-bot | <tuan.hoang1> disk image is used instead of initrd image | 14:35 |
*** lpetrut has quit IRC | 15:27 | |
*** lpetrut has joined #kata-general | 16:39 | |
*** lcastell has joined #kata-general | 16:55 | |
*** sameo_ has quit IRC | 17:07 | |
*** lpetrut has quit IRC | 17:18 | |
kata-irc-bot | <claire> Several important CFP deadlines are coming in hot! * 1/18 *TOMORROW* - KubeCon/CloudNativeCon EU in Barcelona May 20-23 - https://events.linuxfoundation.org/events/kubecon-cloudnativecon-europe-2019/cfp/ * 1/18 *TOMORROW* - Dockercon 2018 in San Francisco April 29-May 2 - https://dockercon19.smarteventscloud.com/portal/cfp/cfpLogin.ww * 1/21 *MONDAY* - Open Networking Summit in San Jose April 3-5 - | 17:21 |
kata-irc-bot | https://events.linuxfoundation.org/events/open-networking-summit-north-america-2019/program/cfp/ — And last but not least! — * 1/23 *NEXT WEDS*- Open Infrastructure Summit in Denver April 29-May 1 - https://www.openstack.org/summit/denver-2019/. Make sure to submit to this one! Please add your Kata submissions to this tracker: https://etherpad.openstack.org/p/KataTalks2019. Thanks! | 17:21 |
*** sameo_ has joined #kata-general | 17:46 | |
*** gwhaley has quit IRC | 18:04 | |
*** sameo_ has quit IRC | 19:29 | |
*** lpetrut has joined #kata-general | 19:35 | |
*** lpetrut has quit IRC | 20:36 | |
*** irclogbot_0 has quit IRC | 20:41 | |
*** irclogbot_0 has joined #kata-general | 20:51 | |
*** stackedsax has joined #kata-general | 23:25 |
Generated by irclog2html.py 2.15.3 by Marius Gedminas - find it at mg.pov.lt!