Currently, when the 'docker-machine' command fails, we only logs "exit status 1' Which is not very helpful in root cause analysis. With this patch, the 'docker-machine' command's stderr output is also logged. # To cause docker-machine command fail $ export DOCKER_MACHINE_NAME=xx $ k3d create 2019/06/13 16:45:31 Created cluster network with ID 6fc91e0e5e912443e6b847f113a6a0bb85ccd610e5232592296d4b199f0347cf 2019/06/13 16:45:31 Error executing 'docker-machine ip' 2019/06/13 16:45:31 Docker machine "xx" does not exist. Use "docker-machine ls" to list machines. Use "docker-machine create" to add a new one. exit status 1
k3d
k3s in docker
k3s is the lightweight Kubernetes distribution by Rancher: rancher/k3s
This repository is based on @zeerorg's zeerorg/k3s-in-docker, reimplemented in Go by @iwilltry42 in iwilltry42/k3d, which is now rancher/k3d.
Requirements
Get
You have several options there:
- use the install script to grab the latest release:
- wget:
wget -q -O - https://raw.githubusercontent.com/rancher/k3d/master/install.sh | bash - curl:
curl -s https://raw.githubusercontent.com/rancher/k3d/master/install.sh | bash
- wget:
- Grab a release from the release tab and install it yourself.
- Via go:
go install github.com/rancher/k3d(Note: this will give you unreleased/bleeding-edge changes)
or...
Build
- Clone this repo, e.g. via
go get -u github.com/rancher/k3d - Inside the repo run
- 'make install-tools' to make sure required go packages are installed
- Inside the repo run one of the following commands
make buildto build for your current systemgo installto install it to yourGOPATH(Note: this will give you unreleased/bleeding-edge changes)make build-crossto build for all systems
Usage
Check out what you can do via k3d help
Example Workflow: Create a new cluster and use it with kubectl
k3d createto create a new single-node cluster (docker container)export KUBECONFIG=$(k3d get-kubeconfig)to makekubectlto use the kubeconfig for that cluster- execute some commands like
kubectl get pods --all-namespaces k3d deleteto delete the default cluster
What now?
Find more details under the following Links:
Connect
- Join the Rancher community on slack via slack.rancher.io
- Go to rancher-users.slack.com and join our channel #k3d
- Start chatting
Languages
Go
89.6%
Shell
8.3%
Makefile
1.7%
Dockerfile
0.4%