Package Details: kind 0.14.0-1

Git Clone URL: https://aur.archlinux.org/kind.git (read-only, click to copy)
Package Base: kind
Description: Kubernetes IN Docker - local clusters for testing Kubernetes
Upstream URL: https://kind.sigs.k8s.io/
Keywords: cluster container docker kubernetes testing
Licenses: Apache
Submitter: matthias.lisin
Maintainer: matthias.lisin
Last Packager: matthias.lisin
Votes: 2
Popularity: 0.35
First Submitted: 2020-03-21 03:21 (UTC)
Last Updated: 2022-05-19 23:45 (UTC)

Latest Comments

matthias.lisin commented on 2022-06-22 17:09 (UTC)

@thurstylark kind supports podman without the need to have a docker executable or wrapper. The choice is between docker and podman which can be installed side-by-side. Forcing the user to choose between docker an podman-docker would suggest it's either or. But I see your point and I'll think about it. I feel like I had already played around with kind + podman-dnsname and ended up choosing not to include it. Hope I'll be able to remember the reason for my decision.

thurstylark commented on 2022-06-14 03:51 (UTC)

Because podman-docker provides docker and depends on podman, it should now be sufficient to move docker to the depends array, and remove podman from the optdepends array. When a user installs this package, but does not have either docker or podman installed, pacman will ask the user to pick one from a list of packages that provide docker, and podman-docker will be in that list. (this is something that has been set up by the maintainer of podman-docker, and may not have been the case when this was being discussed a year ago)

As for podman-dnsname, I would suggest adding that to the optdepends array with a comment along the lines of "required when using podman in place of docker". podman-dnsname has a hard dep on dnsmasq, so you shouldn't need to mention dnsmasq (also something that might have changed since this was discussed)

Since users are shown a list of optdepends and their comments in pacman's output, I think both of these changes should be all you need to communicate what's necessary to the user.

miguescri commented on 2021-06-16 14:45 (UTC)

@matthias.lisin I'm not familiar with the PKG syntax for complex dependencies, so can't suggest anything about it. The only thing I can think about is explaining the situation in a message at the end of the installation process and leave the installation up to the user. Anyway, KinD is quite of a niche software, so I hope users will understand the situation and the need of a container engine in the host.

matthias.lisin commented on 2021-06-16 05:37 (UTC)

@miguescri I kinda jumped the gun on podman tbh. Couldn't properly communicate in the PKGBUILD that you need either docker or podman, podman-dnsname and dnsmasq. Not quiet sure myself why I chose that route.

I'll put the podman packages back in optdepends, and also keep docker there. Gonna look a bit ugly because those two packages don't have a common provides to trigger a XOR choice when installing kind. Although podman needs podman-dnsname, and podman-dnsname needs dnsmasq, their depends doesn't reflect that. It will look a bit messy.

I appreciate any suggestions on how to handle this.

miguescri commented on 2021-06-15 21:06 (UTC)

Why is now Podman a required dependency and Docker optional?