Skip to content

docs(imageless-kubernetes): FloxHub login prereq + schema-aware runtime key #139

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
stephenyeargin merged 1 commit into from
Oct 27, 2026
Merged

docs(imageless-kubernetes): FloxHub login prereq + schema-aware runtime key #139

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
13 changes: 13 additions & 0 deletions imageless-kubernetes/examples/kind-demo.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -9,6 +9,19 @@ Kubernetes deployment, but you don't have to build a container image.
To demonstrate this, we'll run a simple web server backed by Redis using two
Flox environments.

## Prerequisites

Before you start, make sure you have:

- [Flox installed](/install-flox/install)
- A FloxHub login — run [`flox auth login`](/man/flox-auth)

The example pulls its Flox environments from FloxHub, so the shim needs a
FloxHub token. `just up` copies your token into a Kubernetes secret for you
and stops with an error if you are not logged in. See
[Configuration](/imageless-kubernetes/config) for how that secret is created
and mounted.

## Running the example

The entirety of this example can be run locally with the following commands:
Expand Down
2 changes: 1 addition & 1 deletion imageless-kubernetes/install/troubleshooting.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -23,7 +23,7 @@ Verify the Flox runtime configuration is present in the active containerd config

2. Check if `containerd config dump` has an `imports` section that might be loading other configuration files.

3. Confirm the relevant sections exist in the output:
3. Confirm the relevant sections exist in the output. The plugin id depends on your containerd config schema version — `io.containerd.grpc.v1.cri` for `version = 2` (shown below) and `io.containerd.cri.v1.runtime` for `version = 3` or `4`. See [Self-managed installation](/imageless-kubernetes/install/self-managed) for both forms.

```toml
[plugins."io.containerd.grpc.v1.cri".containerd.runtimes.flox]
Expand Down
Loading