| kata-irc-bot | <zeroping> I'm trying to get started, and I can tell that the preferred setup is Fedora/Centos or to use snap on x86_64. I'm straying off that path, and am trying to figure out which of the non-preferred options is best. | 15:50 |
|---|---|---|
| kata-irc-bot | <zeroping> How baked is the aarch64/arm64 support? | 15:51 |
| kata-irc-bot | <zeroping> Likewise, how screwed am I if I don't stick to https://github.com/kata-containers/kata-containers/blob/main/versions.yaml? | 15:52 |
| kata-irc-bot | <zeroping> My preferred system is Debian stable on ARMv8, but that's cgroups v2 and containerd 1.4.5 by default. My first couple of attempts haven't gone well... | 15:56 |
| kata-irc-bot | <jakob.naucke> We distribute in a number of ways. Not claiming an exhaustive list: • Packages on Fedora (x86_64 & aarch64 supported since 34 I think, ppc64le & s390x on rawhide) • kata-deploy, where you `kubectl apply` a file on your cluster and it installs Kata into `/opt/kata`. x86_64 only at this time if I'm not mistaken. • GitHub releases, which have the same `/opt/kata` tarball, dto. x86_64. • Snaps for all platforms So to get bac | 16:17 |
| kata-irc-bot | your question about ARM without Snaps and Fedora: I think you will have to build it yourself, but a normal `make` (which builds the tarball mentioned above) might just work? I guess you'll have to continue from the containerd guide after building it, untarring it to `/`, and linking to `/opt/kata/bin/containerd-shim-kata-v2` somewhere in your PATH. > How baked is the aarch64 support? I don't have hardware to test personally, but packaging | 16:17 |
| kata-irc-bot | aside, it is a tested platform. cc @jianyong.wu > not sticking to `versions.yaml` Depends. > cgroups v2 Might need to disable. > containerd 1.4.5 Might not work. cc @fupan | 16:17 |
| kata-irc-bot | <zeroping> That's quite helpful, and I had vaguely known much of it. Glad to hear that aarch64 doesn't sound too unusual - that's hard to change :slightly_smiling_face: | 16:26 |
| kata-irc-bot | <zeroping> I've attempted some hybrid of the manual install and compiling from source. I was getting into the weeds with error messages that Google had never seen before. | 16:28 |
| kata-irc-bot | <zeroping> I ran into issues that smelled like a problem with cgroups v2, so set the kernel args to use v1 for now | 16:28 |
| kata-irc-bot | <zeroping> I can also say that fedora 34 binaries were not happy running with the older debian stable glibc, so that was out (else, converting packages with alien might be a clean route) | 16:30 |
| kata-irc-bot | <zeroping> Current issue looks like it starts QEMU, but quickly stops hearing from it via QMP. | 16:37 |
| kata-irc-bot | <zeroping> (Not that I know what QMP is yet, but I gather it's the communication channel used to chat with QEMU, so perhaps QEMU has died?) | 16:38 |
| kata-irc-bot | <zeroping> Debian Stable is QEMU 5.2, and it looks like 5.1 might be the recommended for aarch64, while 6.1 is recommended for x86_64? | 16:38 |
| kata-irc-bot | <zeroping> Based on your comments though, I'm guessing my issues are less "user is on funny ARM system" and more "user didn't install the recommended versions of the dependencies". | 16:40 |
| kata-irc-bot | <zeroping> So maybe I'll give Debian testing (containerd 1.5.8) a quick try. | 16:42 |
| kata-irc-bot | <jakob.naucke> > error messages that Google had never seen before If you're unsuccessful in resolving, feel free to post here or on GitHub. > Fedora 34 binaries were not happy running with the older debian stable glibc yeah no, I generally would expect that to not work > looks like it starts QEMU, but quickly stops hearing from it via QMP if it's something like "timed out connecting to vsock", that's unfortunetaly just the generic "something | 17:31 |
| kata-irc-bot | went wrong, I can't reach the agent" error > Not that I know what QMP is yet, but I gather it's the communication channel used to chat with QEMU the QEMU Machine Protocol, yes > Debian Stable is QEMU 5.2, and it looks like 5.1 might be the recommended for aarch64, while 6.1 is recommended for x86_64? I'm not sure but it might work at this point, see https://github.com/kata-containers/kata-containers/pull/2732 | 17:31 |
| kata-irc-bot | <zeroping> re fedora binaries via alien: I though maybe they might work on Debian testing, but no luck - Fedora 34 is 2.33, while Debian testing is still 2.32. I had to try tho - it was a quick experiment. | 17:38 |
| kata-irc-bot | <zeroping> I think the specific error is along the lines of: `scanner return error: read unix @->/run/vc/vm/test-kata/qmp.sock: use of closed network connection` right after reading QMP capabilities. Probably best if I try the correct containerd before chasing it too far. | 17:44 |
| kata-irc-bot | <jakob.naucke> Hmm, that narrows it down... a little. Yes, please do try containerd 1.5 if you can. Debug messages can help (yay, we've hit the developer guide already), at a certain point of certainty on your side it's also worth an issue. I take it you're using `ctr`/`nerdctl`? | 17:47 |
| kata-irc-bot | <zeroping> Yep, ctr. Definitely not at any level of certainty yet, and trying not to bother people too much until I am. | 17:49 |
| kata-irc-bot | <zeroping> (hilariously, I have an installation of containerd 1.5.8ish on the host already, from playing with firecracker-containerd, so maybe I'll test with that before trying bits from Debian testing) | 17:51 |
| kata-irc-bot | <zeroping> I'll get to trying it in a day or two. Thanks for the help and suggestions, and pointing out my most likely places to look. That intuition is hard to acquire. | 17:54 |
Generated by irclog2html.py 2.17.2 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!