Arch Linux User Repository

As a person not associated with the project, at this point I have no idea. I'll chalk it up to the same uncertainty as with the release timing.

Thanks for linking to the documentation, it'll probably need a bit of expanding for Podman, as well, but looks like a good starting point.

Thanks for your take on this. I'm also curious: Do you happen to know whether kata packaging is going to be drastically different for version 2 or whether it'll be mostly the same?

Basically, would it be useful/wise to even officially package kata 1?

About the wiki page: Thanks! That'd be a good first step for making kata on Arch quite a bit more approachable. I suppose it could borrow a lot from https://github.com/kata-containers/documentation/blob/master/install/docker/debian-docker-install.md

If Kata's tag history is any guidance, the closest one can get to measurable anticipation of a stable release is about 2 weeks to a month after upstream posts an RC and since there is none for 2.0, nobody knows for sure.

The other thing is Kata's (optional from a package maintenance standpoint) support for other hypervisors - as of the time of writing, Firecracker and Cloud-Hypervisor, whose adoption would provide a more complete scope of software's possibilities.

As for the Wiki article - that's largely dependent on the time budget I'll end up having left and the time frame it'd have to fit in, but I'll give it a shot.

I'm potentially interested in maintaining this set of packages in [community] as I think this could be pretty cool for infra stuff. However, I'm curious as to whether we should wait for kata 2? Also, would you be interested in writing a Kata Containers ArchWiki article perhaps?

Thanks psYchotic.

Bump version to 1.9.3-8.1: https://git.sr.ht/~otaconix/aur-kata-containers/commit/ba45411116334eff6b760b0cebb45e91223d258e

@kshlm yup, just drop in kata = ["/usr/bin/kata-runtime"] under the [runtimes] section in /etc/containers/libpod.conf (example file in /usr/share/containers/libpod.conf), run podman -ti --runtime=kata alpine:edge /bin/sh and it Just Works™.

From a brief skim, if podman is as drop-in as it claims, it shouldn't be too difficult to point it to another runtime, like Kata.

Thanks again for the patch zer0def. I've updated to 1.8.2.

I've moved to using podman over docker, and no longer use kata-containers. I'm orphaning this package,

1.8.0 to 1.8.2 bump: https://github.com/zer0def/PKGBUILDs/commit/7a0cc30e2e5b4773ed3acf72ec27f564623eebf1.patch