Custom CRI runtime#
k0s supports users bringing their own CRI runtime (for example, docker). In which case, k0s will not start nor manage the runtime, and it is fully up to the user to configure it properly.
To run a k0s worker with a custom CRI runtime use the option
It takes input in the form of
dockerfor pure docker setup,
remotefor anything else.
socket: Path to the socket, examples:
To run k0s with pre-existing docker setup run the worker with
k0s worker --cri-socket docker:unix:///var/run/docker.sock <token>.
docker is used as a runtime, k0s will configure kubelet to create the dockershim socket at