docs: add Rancher (RKE2/K3s) install instructions - #212
Merged
Merged
Conversation
RKE2 and K3s run their embedded containerd on /run/k3s/containerd/containerd.sock, so extension-container needs that socket configured. The OCI runtime root stays at the default, as containerd keeps its runc state under /run/containerd/runc/k8s.io regardless of the socket location.
joshiste
force-pushed
the
docs/rancher-install-instructions
branch
from
September 3, 2026 10:45
5e89e81 to
5658e9b
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds an "Alternative: Rancher (RKE2 / K3s) installation" section to the Kubernetes install page, alongside the existing OpenShift and GKE Autopilot alternatives.
RKE2 and K3s run an embedded containerd whose socket lives at
/run/k3s/containerd/containerd.sock, which the chart cannot auto-detect — the extension pods otherwise hang inContainerCreatingwithhostPath type check failed: /run/containerd/containerd.sock is not a socket file.The section documents:
extension-container.containerEngines.containerd.socket)ociRuntime.root— containerd keeps its runc state under/run/containerd/runc/k8s.ioregardless of where the socket lives, and/run/k3s/containerd/runc/k8s.iodoes not exist, so overriding it breaks theociruntime-roothostPath mountVerified end-to-end on a k3s v1.35.5 cluster (containerd 2.2.3-k3s1): agent + extensions installed via the umbrella chart with only the socket override, container discovery reported targets, and a stress-CPU attack ran to completion (which exercises the OCI runtime root). RKE2 uses the same embedded k3s containerd socket path but was not tested directly.