| kata-irc-bot | <bergwolf> Thanks @zkaiser! Will update the slides for future reference. | 08:37 |
|---|---|---|
| kata-irc-bot | <norbj.d_kata> :wave: qemu with snapshotter devmapper works :thinking_face: | 12:36 |
| kata-irc-bot | <norbj.d_kata> before continuing since I can't really make it work, do you have benchmarks of kata-qemu vs kata-firecracker starting ? because I just wanted to benchmark both to check cold start :slightly_smiling_face: if firecracker is better than qemu I should continue to try to make it work, but if not I don't really need to continue I guess :D | 12:38 |
| kata-irc-bot | <norbj.d_kata> with kata 2.1.1 (the latest version working on my VM :P) I got these results: ```\time -f %e nerdctl run --rm -it --runtime io.containerd.run.kata.v2 ubuntu echo # average: 2.05 seconds \time -f %e nerdctl run --rm -it --snapshotter=devmapper --runtime io.containerd.run.kata-fc.v2 ubuntu echo # average: 2.85 seconds``` by any chance, do you know if kata-fc starts more quickly than kata-qemu? by the way i'm surprised of these | 13:12 |
| kata-irc-bot | results since firecracker is told to start quicker than qemu :thinking_face: | 13:12 |
| kata-irc-bot | <anastassios.nanos> yea, so, regarding numbers we've haven't properly benchmarked boot times -- to do that right we would need to spend some time adding hooks so it might take a while, but we'll definitely do that in the next weeks. regarding the difference, you're using a different snapshotter, so I suspect there's some extra overhead related to the setup of the devmapper device compared to the virtiofs process in the default kata | 14:15 |
| kata-irc-bot | <anastassios.nanos> OK so ;) | 15:31 |
| kata-irc-bot | <anastassios.nanos> the issue seems to be with the rootfs image | 15:31 |
| kata-irc-bot | <anastassios.nanos> for now you can just get the 2.1.1 .img and place it in the 2.4.1 location /opt/kata/share/kata-containers/kata-containers.img and it should work fine | 15:32 |
| kata-irc-bot | <anastassios.nanos> not sure what's causing this -- I suspect something got fucked up with the image build process? with systemd? not sure... | 15:32 |
| kata-irc-bot | <anastassios.nanos> | 15:33 |
| kata-irc-bot | <anastassios.nanos> we'll dig into it once we get the chance -- in the meantime, let me update the gh issue just to make sure we've tracked that correctly | 15:34 |
| kata-irc-bot | <norbj.d_kata> thank you very much! indeed it works :grinning: :+1: | 15:48 |
| kata-irc-bot | <anastassios.nanos> ok, so building from source using ubuntu as the rootfs and clearlinux as the rootfs seems to work fine for kata-FC 2.4.1 | 17:47 |
| kata-irc-bot | <anastassios.nanos> so there has to be some option we're using in the static/release build for the rootfs that fc does not like | 17:47 |
| kata-irc-bot | <anastassios.nanos> @fidencio who can point us to the scripts that build the rootfs for the release / static build ? | 17:48 |
| kata-irc-bot | <fidencio> I can, gimme a few minutes :slightly_smiling_face: | 18:04 |
| kata-irc-bot | <fidencio> Basically, the release process just calls https://github.com/kata-containers/kata-containers/blob/a80eb33cd6b1f3dbb42080ff30a161781d2f151a/.github/workflows/release.yaml#L31 That one will end up calling functions from this file: https://github.com/kata-containers/kata-containers/blob/main/tools/packaging/guest-image/build_image.sh | 18:09 |
| kata-irc-bot | <fidencio> (for the rootfs) | 18:09 |
| kata-irc-bot | <anastassios.nanos> ok thanks, will try to repro the issue | 18:51 |
| kata-irc-bot | <anastassios.nanos> ok so that's weird ;) | 19:46 |
| kata-irc-bot | <anastassios.nanos> works if I build it by hand | 19:47 |
| kata-irc-bot | <norbj.d_kata> if that can help, i have tried to build the `main` branch too using these commands I found in the github actions: ```KATA_ASSET=rootfs-image TAR_OUTPUT=$KATA_ASSET.tar.gz ./tools/packaging/kata-deploy/local-build/kata-deploy-copy-yq-installer.sh ./tools/packaging/kata-deploy/local-build/kata-deploy-binaries-in-docker.sh --build="${KATA_ASSET}" build_dir=$(readlink -f build) cp -r "${build_dir}" "kata-build"``` and then packaging | 19:51 |
| kata-irc-bot | the whole with: ```./tools/packaging/kata-deploy/local-build/kata-deploy-merge-builds.sh``` and it didn't work for me :( | 19:51 |
Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!