This message was deleted.
# k3s
a
This message was deleted.
c
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?
m
Should I create issue to https://github.com/containerd/nerdctl ?
c
Probably a good start yeah
m
@creamy-pencil-82913 btw, where are buildctl and runc?
runc is necessary, right? Is it bundled as part of some k3s binary? I guess buildctl is not necessary, but can/should it be included in k3s installation?
c
I don’t know what buildctl is; it’s not something we provide. runc is packaged within k3s
m
@creamy-pencil-82913 buildctl is part of buildkitd, which I believe is part of k3s. https://github.com/moby/buildkit#quick-start
c
It is not. We don't include buildkit, nerdctl, or any of that.
m
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?
c
correct. K3s is just kubernetes + containerd
2
All the extra developer tooling that comes with Rancher Desktop does not come from K3s.
m
Undestood! Thanks for clarification.
k
nerdctl compose -f compose.yml down && nerdctl rmi -f containerName
nerdctl compose -f compose.yml down && nerdctl rmi -f containerName
271 Views