Package Details: k3s-bin 1.23.5+k3s1-1

Git Clone URL: (read-only, click to copy)
Package Base: k3s-bin
Description: Lightweight Kubernetes
Upstream URL:
Keywords: kubernetes
Licenses: Apache
Conflicts: k3s-git
Submitter: duxet
Maintainer: galdor
Last Packager: galdor
Votes: 21
Popularity: 0.64
First Submitted: 2019-02-28 07:14 (UTC)
Last Updated: 2022-04-12 13:02 (UTC)

Latest Comments

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 "" 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 - 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


galdor commented on 2022-01-03 06:36 (UTC)

Updated to 1.22.5+k3s1.

galdor commented on 2021-12-09 08:38 (UTC)

Updated to 1.22.4+k3s1.

galdor commented on 2021-11-05 08:24 (UTC)

Updated to 1.22.3+k3s1.

francescortiz commented on 2021-10-08 11:27 (UTC)

Awesome, thanks!

galdor commented on 2021-10-08 10:45 (UTC)

Got it. Including this script would be indeed a good idea. The problem is that it currently is generated by the k3s install script, meaning that we cannot easily make it part of the package.

I have open an issue on the k3s repository; I will add it to the package as soon as they start releasing this script.

francescortiz commented on 2021-10-07 13:53 (UTC)

It is part of the official k3s tooling. You can check it here:

Also, it is referenced inside the install script of k3s: (look for KILLALL_K3S_SH).

galdor commented on 2021-10-07 09:24 (UTC)

Updated to 1.22.2+k3s2.

galdor commented on 2021-10-03 12:13 (UTC)

Where does this script comes from ? There is no source or author.

francescortiz commented on 2021-10-03 10:43 (UTC)

Why don't you include like does?

galdor commented on 2021-09-27 09:06 (UTC)

Updated to 1.22.2.

galdor commented on 2021-09-17 14:44 (UTC)

Updated to 1.21.4.

satcom886 commented on 2021-03-16 10:17 (UTC)

@txomon Oh yeah! Please add the backup line, that would really avoid many headaches.

txomon commented on 2021-03-16 09:42 (UTC) (edited on 2021-03-16 10:08 (UTC) by txomon)

I would recommend to just copy the original to /etc/systemd/system/k3s.service replacing there k3s server with k3s agent.

Also, please update the PKGBUILD to include a backup line like amiga23 said

satcom886 commented on 2021-02-18 15:31 (UTC)

@Vanilla Thanks, I also started using systemctl edit so the edits survive updates. It still seems kind of hacky tho.

Vanilla commented on 2021-02-18 13:11 (UTC) (edited on 2021-02-18 13:44 (UTC) by Vanilla)


<del>I notice the k3s.service.env installed inside /etc/systemd/system. According to the Getting Started section of the K3S docs, by specifying K3S_URL and K3S_TOKEN, the K3S can be instructed to run in agent mode. (Not tried yet.)</del>

I was wrong. That trick is only for its installation script instead of the K3S binary. In order to run a K3S agent, now I have to partially overwrite the shipped service file with systemctl edit k3s.service .

galdor commented on 2021-01-05 06:21 (UTC)

Would it be possible to add a k3s group and use it for /etc/rancher/k3s/k3s.yaml ? In the current state, the file is owned by root and is 0600, but this file must be readable by any kubernetes tool such as kubectl.

satcom886 commented on 2020-12-06 09:46 (UTC)

I have a possibly dumb question, but how do you "oficially" choose between server and agent mode?

I edited /usr/lib/systemd/system/k3s.service and replaced k3s server with k3s agent. I'm guessing that this is not the right way...

i.further commented on 2020-11-16 15:33 (UTC)

The some files is not removed when it removed.

amiga23 commented on 2020-06-02 07:04 (UTC)

Please do not override the config file during update.


mercutio commented on 2020-02-04 10:29 (UTC)

I updated the package to 1.17.2, in case someone else might find it useful:

tbrock commented on 2020-01-03 22:27 (UTC)

It looks like that commit did update them, the shas must have changed since the initial publish. Anyway, they are correct now. Enjoy!

tbrock commented on 2020-01-03 19:26 (UTC)

Ah I'm sorry I use a script that runs updpkgsums and it must not have updated all of them for some reason, I just published a pkgrel 2 verson that should do the trick.

isra17 commented on 2020-01-03 14:55 (UTC)

valid sha (From my result and as advertisied in the sha256sum-amd64.txt) is c7c5d39a60fa0665913f83cee78eb0c440cbd7c9e2e85783f10a2bba09d977ee

isra17 commented on 2020-01-03 14:50 (UTC)

Source k3s-1.0.1-x86_64 does not pass validity test anymore.

FranklinYu commented on 2019-11-15 07:49 (UTC)

This is fantastic. Thank you for packaging!

tbrock commented on 2019-10-29 13:38 (UTC)

TheAifam5 thanks for the suggestions. I've updated the PKGBUILD with some of them.

theaifam5 commented on 2019-10-15 13:37 (UTC) (edited on 2019-10-15 13:38 (UTC) by theaifam5)

Much better and in arm* the x86_64 are useless (so why to download them?), here how it should be done:

JamieMagee commented on 2019-08-07 07:28 (UTC)

The pkgrel in .SRCINFO and PKGBUILD don't match