Arch Linux User Repository

This package only contains the stable release of rancher's k3d.
If you're intereseted in pre-release/beta versions, head over to rancher-k3d-beta-bin

Please bump to v5.6.0

Would you consider adding an installation step for completions?

Something along the lines of:

/usr/bin/k3d completion bash | install -Dm644 /dev/stdin "$pkgdir/usr/share/bash-completion/completions/k3d"
/usr/bin/k3d completion zsh | install -Dm644 /dev/stdin "$pkgdir/usr/share/zsh/site-functions/_k3d

@lira is correct... I had to revert to 5.12.1-arch1-1. Greater than that k3d was unstable... Check uname -a.

Then if your pacman cache hasn't been flushed

sudo pacman -U /var/cache/pacman/pkg/linux-5.12.1.arch1-1-x86_64.pkg.tar.zst /var/cache/pacman/pkg/linux-headers-5.12.1.arch1-1-x86_64.pkg.tar.zst

To prevent overriding the kernel downgrade, I then added an entry like so IgnorePkg = linux to /etc/pacman.conf.

Filed an issue

https://github.com/rancher/k3d/issues/604

I couldn't find the reason but the k3d doesn't work with th linux kernel 5.12.2.arch1-1. I exported the var K3D_FIX_CGROUPV2=1 but it didn't work. I've downgraded the kernel to the 5.12.1.arch1-1 and k3d has worked as expected.

@zer0def

Of course not, especially with that nice patch attached! Thanks for the help, 1.7.0-3 contains arm and aarch releases :)

Hey Johnny, would it be much of a bother to add support for other architectures?: https://github.com/zer0def/PKGBUILDs/commit/1e3d7bc99a610115a4a7d17db9d571668a7fc747.patch

This package only contains the stable release of rancher's k3d.
If you're intereseted in pre-release/beta versions, head over to rancher-k3d-beta-bin

I'm not sure if we should update the package to pre release versions, will do some research on how to handle this on the aur normally.

Here's a patch for 3.0.0-rc0

index b08cfdd..cddb653 100644
--- a/PKGBUILD
+++ b/PKGBUILD
@@ -1,14 +1,14 @@
 # Maintainer: Jonas Dellinger <jonas@dellinger.dev>
 pkgname="rancher-k3d-bin"
-pkgver=1.7.0
+pkgver='3.0.0_rc.0'
 pkgrel=1
 pkgdesc='Little helper to run Rancher Labs k3s in Docker'
 arch=('x86_64')
 url='https://github.com/rancher/k3d'
 license=('MIT')
 provides=("k3d")
-source=("${pkgname}-${pkgver}::https://github.com/rancher/k3d/releases/download/v$pkgver/k3d-linux-amd64")
-sha256sums=('da9ff31bcf4377fadfb065f4998d347f19de1168a5a553ce2c23b763ee1f6098')
+source=("${pkgname}-${pkgver}::https://github.com/rancher/k3d/releases/download/v${pkgver/_/-}/k3d-linux-amd64")
+sha256sums=('7564c701eecbba57622f2df833ed393b60affbf36281f6cb2f219efb1be78646')

 package() {
   install -Dm 0755 ${pkgname}-${pkgver} "$pkgdir/usr/bin/k3d"

@dg10a

I'm fairly new to the AUR, so correct me if I'm wrong. I decided to keep the original binary name k3d because that's what the upstream package is called. I'm not sure if it is common to rename the binaries of upstream packages? Do we have some example where this is done?

This package provides k3d, which is a different program entirely

I think we already have a lot of programs which have name clashes. Even your linked k3d has a wrong package name IMO, it should be k-3d.