k3d
k3d.io
- Free plan
- Windows
- macOS
- Linux
- Self-hosted
What k3d is
k3d is a lightweight wrapper for running k3s, Rancher Lab’s minimal Kubernetes distribution, in Docker. It creates single-node and multi-node clusters, including for local Kubernetes development, and can support workflows such as code hot-reloading or a build-deploy-test cycle with Tilt. Docker is required, and kubectl is used to interact with a cluster. For k3d v5.x.x, the overview specifies Docker v20.10.5 or later and runc v1.0.0-rc93 or later for proper operation. The community-driven project is not an official Rancher (SUSE) product; its Free plan is free, with sponsorships supporting development. It runs on Linux, macOS, and Windows. Cluster configuration can use registries.yaml for registry authentication and certificates, and the documentation covers local registries, including ones managed by k3d. Services can be exposed through Ingress or NodePort by mapping container ports to the host. Installation options include GitHub release binaries, Homebrew, AUR, Chocolatey, Scoop, arkade, asdf, and Go.
Who it suits
k3d suits developers who need local single-node or multi-node Kubernetes clusters in Docker, including for development workflows. It requires Docker, and users interact with clusters through kubectl.
Good to know, and what to watch
- Creates single-node and multi-node k3s clusters.
- Runs on Linux, macOS, and Windows.
- Supports local registries and registry configuration.
- Documents Ingress and NodePort service exposure.
- Offers multiple installation methods.
- Requires Docker.
- The project is not an official Rancher (SUSE) product.
- k3d v5.x.x specifies minimum Docker and runc versions.
Plans
Every plan and priceFree
Free plan
The verdict
k3d provides a Docker-based way to create local k3s clusters, with documented registry configuration and service exposure. Check its Docker and runc requirements, and note that it is community-driven rather than an official Rancher product.
What the maker publishes
- Cluster configuration
- A registries.yaml file can configure registries for a cluster, and the configuration can include registry authentication and certificates. source
- Cluster creation
- It creates single-node and multi-node k3s clusters in Docker, including for local Kubernetes development. source
- Community status
- k3d is community-driven and is not an official Rancher (SUSE) product. source
- Development and CI use
- The overview lists demo use cases including code hot-reloading, a build-deploy-test cycle using Tilt, and running k3d as a service in Drone CI. source
- Docker version
- The overview says k3d v5.x.x requires at least Docker v20.10.5 with runc at least v1.0.0-rc93 to work properly. source
- Ingress
- The service guide notes that k3s deploys Traefik as its default ingress controller and demonstrates accessing an Ingress through a mapped host port. source
- Installation
- The maker lists installation options including GitHub release binaries, Homebrew, AUR, Chocolatey, Scoop, arkade, asdf, and Go. source
- Kubernetes integrations
- The k3s features guide covers CoreDNS, local-path-provisioner, Traefik, and the Klipper service load balancer in k3d. source
- Local registries
- The documentation describes creating and using local container image registries, including registries managed by k3d. source
- Purpose
- k3d is a lightweight wrapper for running k3s, Rancher Lab’s minimal Kubernetes distribution, in Docker. source
- Related tools
- The overview links to a VS Code extension for handling k3d clusters and a Linux graphical interface called k3x. source
- Requirements
- Docker is required to use k3d, and kubectl is used to interact with the Kubernetes cluster. source
- Service exposure
- The service guide documents exposing services through Ingress or NodePort by mapping container ports to the host. source
- Support
- The overview directs users to the Rancher community Slack and its #k3d channel for discussion. source
Checked against the maker's pages on 7 Oct 2026.