That will open your browser to the Kubernetes dashboard. Start the Minikube dashboard by running % minikube dashboard █. You should see a message that the deployment was created. Run % kubectl apply -f basic_deployment.yaml █ to create the deployment. imagePullPolicy: Never tells Kubernetes that the image exists locally, i.e. The important parts are the image name which needs to match the tag we gave in docker build, the imagePullPolicy, and the selector: matchLabels which will be used for networking later. We need to create a deployment file which instructs Kubernetes on how to run our application. Now to run the container in Kubernetes, we’ll start to touch the surface of infrastructure as code. We’ve successfully built and run a container in docker, next we’ll run it on Kubernetes. Direct your browser to to see the output of index.html. Next run % docker run -p 8787:80 basic-nginx █ to start the container. After installing kubectl, try running % kubectl config get-contexts █. A cluster and the authentication details needed to access it are collectively known as a context. You’ll use it in production and development. Kubectl is a command line tool that allows you to interact with a Kubernetes cluster. After installing, start it with: % minikube start -vm=true █ And finally install kubectl. It’s not production ready but it’s perfect for learning and testing. Minikube is a development focused Kubernetes cluster that you can run locally.

Head over to and install the latest stable version. Docker includes a container runtime and tools to build containers. First you’ll need to install docker for working with containers.

Then we’ll move to a production setup using a cloud provider. We’ll start out by learning how to run a miniature cluster on our own computer.

Running docker on kubernetes