Section Developer PoP runs on Kubernetes. Minikube is a miniature, prepackaged Kubernetes cluster that works locally on a desktop Microsoft Windows, Mac or Linux computer.
Minikube runs in the free and open source VirtualBox.
Minikube will start as below.
minikube start 😄 minikube v0.35.0 on darwin (amd64) 🔄 Restarting existing virtualbox VM for "aperture" ... ⌛ Waiting for SSH access ... 📶 "aperture" IP address is 192.168.99.101 🐳 Configuring Docker as the container runtime ... ✨ Preparing Kubernetes environment ... 🚜 Pulling images required by Kubernetes v1.13.4 ... 🔄 Relaunching Kubernetes v1.13.4 using kubeadm ... ⌛ Waiting for pods: apiserver proxy etcd scheduler controller addon-manager dns 📯 Updating kube-proxy configuration ... 🤔 Verifying component health ...... 💗 kubectl is now configured to use "aperture" 🏄 Done! Thank you for using minikube!
Initialize the Developer PoP
minikube ssh "docker run --rm --net=host -v /var/lib/minikube:/var/lib/minikube:ro sectionio/section-init"
Depending on the speed of your internet connection and the power of your computer, the initiation of the Developer PoP can take several minutes.
Unable to find image 'sectionio/section-init:latest' locally latest: Pulling from sectionio/section-init 96ac93103c33: Pull complete 7f806fcb5e6c: Pull complete 9f61142fa1a0: Pull complete fd79b6758639: Pull complete c99a605ef53e: Pull complete Digest: sha256:6619bbb259d0b4f20f8064385a4dad3b1529f825f76ae10867cae11d6a092332 Status: Downloaded newer image for sectionio/section-init:latest namespace "section-bootstrap" created serviceaccount "section-bootstrap" created clusterrolebinding "section-bootstrap-cluster-admin" created deployment "bootstrap" created namespace "section-shared" created service "developer-pop" created
Developer PoP Ready
Now your Developer PoP base is ready, but it has not yet launched any of the specific proxies in your configuration.
Let’s change that by loading your Section setup into the Developer PoP.
Time to Setup
After each one of these terminal commands, you will need to wait a few moments for Minikube to fully launch all the Section containers.
If you, for example, try and do the git pushes in the next section immediately after completing the
minikube ssh command above, you may find that the git daemon or some other relevant component has not yet come online.
In this case, just wait for a few minutes — the exact time depends upon the speed of your internet connection and specifications of your machine.
Disable repeating messages about the kubectl component you won’t need:
minikube config set WantKubectlDownloadMsg false