Package Details: k3s-bin 1.31.1+k3s1-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, k3s-git
Submitter: duxet
Maintainer: galdor
Last Packager: galdor
Votes: 25
Popularity: 0.013678
First Submitted: 2019-02-28 07:14 (UTC)
Last Updated: 2024-10-29 09:41 (UTC)

Latest Comments

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

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 ?

itoffshore commented on 2022-01-16 02:50 (UTC) (edited on 2022-01-16 02:51 (UTC) by itoffshore)

I think it would be useful to create a k3s-bin.install with a post_install() function that sets up the symlinks rancher's install script creates:

ln -sf /usr/bin/k3s /usr/local/bin/kubectl
ln -sf /usr/bin/k3s /usr/local/bin/ctr
ln -sf /usr/bin/k3s /usr/local/bin/crictl

If you download a snapshot of https://aur.archlinux.org/packages/arch-sign-modules/ - you can see an example of how I setup an install file & loop through a list creating symlinks. Also include in the PKGBUILD install="$pkgname.install"

galdor commented on 2022-01-07 06:31 (UTC)

I just released a new version with the two modifications:

  • Mark k3s.service.env for backup by Pacman during updates.
  • Set a finite value for LimitNOFILE in the Systemd definition file.

aber commented on 2022-01-06 19:19 (UTC)

As @amiga23 already pointed out, please do not overwrite k3s.service.env. Adding backup=("etc/systemd/system/k3s.service.env") would improve usability a lot.

nyyu commented on 2022-01-06 19:13 (UTC)

Can you add: backup=("etc/systemd/system/k3s.service.env") Every change to env file is lost after upgrade

Can you update systemd service? There is a perf issue with LimitNOFILE=infinity https://github.com/k3s-io/k3s/commit/b4335630b78b5cf927e79724067803a6c0d7c04f

Thanks.

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