nerdctl system prune --all

doesn’t seem to work with k3s. `$ nerdctl version`:

WARN[0000] unable to determine buildctl version: exec: "buildctl": executable file not found in $PATH
WARN[0000] unable to determine runc version: exec: "runc": executable file not found in $PATH
Client:
 Version:	v0.22.2
 OS/Arch:	linux/amd64
 Git commit:	2899222cb0715f1e5ffe356d10c3439ee8ee3ba4
 builctl:
  Version:

Server:
 containerd:
  Version:	v1.6.6-k3s1
  GitCommit:
 runc:
  Version:

`nerdctl system prune --all`:

WARNING! This will remove:
  - all stopped containers
  - all networks not used by at least one container
  - all images without at least one container associated to them

Are you sure you want to continue? [y/N] y
FATA[0000] needs CNI plugin "firewall" to be installed in CNI_PATH ("/var/lib/rancher/k3s/data/current/bin"), see <https://github.com/containernetworking/plugins/releases>: exec: "/var/lib/rancher/k3s/data/current/bin/firewall": stat /var/lib/rancher/k3s/data/current/bin/firewall: no such file or directory

`cat /etc/nerdctl/nerdctl.toml`:

address        = "unix:///run/k3s/containerd/containerd.sock"
namespace      = "<http://k8s.io|k8s.io>"
snapshotter    = "stargz"
cgroup_manager = "systemd"
cni_path       = "/var/lib/rancher/k3s/data/current/bin"
cni_netconfpath = "/var/lib/rancher/k3s/agent/etc/cni/net.d"

With plain v1.6.6 containerd (RD 1.5.0 in containerd mode with k8s disabled) the commands executed without issues.

This seems like a nerdctl to issue. We don't include any of those binaries or the firewall plugin. Why does it need that plugin just to run a prune?

Should I create issue to https://github.com/containerd/nerdctl ?

Probably a good start yeah

@creamy-pencil-82913 btw, where are buildctl and runc?

I don’t know what buildctl is; it’s not something we provide. runc is packaged within k3s

@creamy-pencil-82913 buildctl is part of buildkitd, which I believe is part of k3s. https://github.com/moby/buildkit#quick-start

It is not. We don't include buildkit, nerdctl, or any of that.

hm, I see. I guess I have misunderstood the architecture, or maybe confused with RD. So RD includes k3s AND buildkitd, but plain k3s doesn’t include buildkitd; is this correct?

correct. K3s is just kubernetes + containerd

Undestood! Thanks for clarification.

nerdctl compose -f compose.yml down && nerdctl rmi -f containerName