Repository navigation
docs(imageless-kubernetes): fix self-managed install for K3s and add verification - #142
Merged
Merged
Conversation
Contributor
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Automations to automatically generate PRs for you. |
devusb
force-pushed
the
docs/imageless-k3s-self-managed
branch
from
October 28, 2026 17:56
4a32daf to
91ee605
Compare
devusb
force-pushed
the
docs/imageless-k3s-self-managed
branch
from
October 28, 2026 18:02
91ee605 to
b93e9c7
Compare
The manual installation steps now work on a fresh node. They note that installing the shim from the catalog requires a FloxHub sign-in, fix the symlink path to match the environment's `-run` directory, and show how to check the containerd version, including on K3s. K3s gets its own configuration steps: the Flox runtime goes in a containerd config template, since K3s regenerates config.toml on every start, and K3s is restarted instead of a containerd service.
…ation steps The automatic installer section now lists the output lines that confirm the shim was installed, and shows how to generate /etc/containerd/config.toml when the installer reports it missing, as happens with containerd packages such as Ubuntu's. The page now ends with steps to apply the sample Pod and check its logs, and notes that kubectl needs sudo with the default K3s kubeconfig.
The steps that differ between distributions now sit in one set of top-level tabs, "containerd" and "K3s", following the platform tabs used on the Flox install pages. Creating the environment and linking the shim stay as shared steps above the tabs.
devusb
force-pushed
the
docs/imageless-k3s-self-managed
branch
from
November 1, 2026 16:49
f85d987 to
f493714
Compare
devusb
marked this pull request as ready for review
November 1, 2026 16:50
stephenyeargin
approved these changes
Nov 3, 2026
This branch was successfully deployed
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
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.
Fixes the self-managed Imageless Kubernetes install page so it works as written on a fresh K3s node, and adds steps that confirm the install worked.
Changes
containerdversion, includingsudo k3s ctr versionon K3s.flox installof the shim requires a FloxHub sign-in (flox auth loginorFLOX_FLOXHUB_TOKEN).-run, not.run. The old glob silently created a dangling link.readlink -echeck for the symlink.config.tomlblocks, then restartcontainerd.config-v3.toml.tmplwith the K3s base template (K3s regeneratesconfig.tomlon each start), restartk3sork3s-agent, then grep the generated config./etc/containerd/config.tomlif it's missing (Ubuntu'scontainerdpackage doesn't create it).kubectlneedssudowith the default K3s kubeconfig.Listening on http://:8080.Testing
Each new command was run on fresh Ubuntu 24.04 nodes, with Flox 1.19.2 and shim/installer 1.1.0:
mint broken-linksreports the same 3 pre-existing broken links on other pages before and after.