Package Details: k3s-bin 1.29.1+k3s2-1

Git Clone URL: https://aur.archlinux.org/k3s-bin.git (read-only, click to copy)
Package Base: k3s-bin
Description: Lightweight Kubernetes
Upstream URL: https://k3s.io
Keywords: kubernetes
Licenses: Apache
Conflicts: k3s-git
Submitter: duxet
Maintainer: galdor
Last Packager: galdor
Votes: 26
Popularity: 1.35
First Submitted: 2019-02-28 07:14 (UTC)
Last Updated: 2024-02-18 13:05 (UTC)

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 Next › Last »

galdor commented on 2023-01-05 12:13 (UTC)

Updated to 1.26.0+k3s1.

galdor commented on 2022-10-16 11:51 (UTC)

Updated to 1.25.2+k3s1.

ayr-ton commented on 2022-10-16 03:09 (UTC)

I volunteer to help with the package upgrade. Feel free to add me as a co-maintainer and I will bump the package to the next version.

galdor commented on 2022-08-29 06:07 (UTC)

Updated to 1.24.4+k3s1.

galdor commented on 2022-04-12 13:04 (UTC)

Updated to 1.23.5+k3s1.

galdor commented on 2022-02-16 07:06 (UTC)

Updated to 1.23.3+k3s1.

vincent.ducamps commented on 2022-02-05 11:23 (UTC) (edited on 2022-02-06 08:43 (UTC) by vincent.ducamps)

Hi when I try to start my K3S instance I have this message anybody else have same?

I0205 12:23:06.662705  218062 state_mem.go:75] "Updated machine memory state"
E0205 12:23:06.712776  218062 kubelet.go:2412] "Error getting node" err="node \"fixe-pc\" not found"
E0205 12:23:06.718178  218062 kubelet.go:1423] "Failed to start ContainerManager" err="failed to initialize top level QOS containers: root container [kubepods] doesn't exist"

first error in log is 

E0206 09:36:54.677300   13450 controller.go:116] loading OpenAPI spec for "v1beta1.metrics.k8s.io" failed with: failed to retrieve openAPI spec, http error: ResponseCode: 503, Body: service unavailable

galdor commented on 2022-01-17 06:42 (UTC)

There is no need to create /usr/local/bin because we should use the same directory as other binaries, i.e. /usr/bin which is already created in the package.

Anyway I will take care of it for the next update.

itoffshore commented on 2022-01-16 21:15 (UTC)

It is easier to create symlinks in post_install() when files / directories exist.

Creating the symlinks in the PKGBUILD means you would also need to create /usr/local/bin before creating the symlinks.

galdor commented on 2022-01-16 19:41 (UTC)

What would be the reason to do that in a separate install script instead of simply adding the symlink in the package function ?

« First ‹ Previous 1 2 3 4 5 6 Next › Last »