{"id":352,"date":"2018-10-16T10:52:50","date_gmt":"2018-10-16T10:52:50","guid":{"rendered":"https:\/\/www.appservgrid.com\/paw93\/?p=352"},"modified":"2018-10-17T08:26:07","modified_gmt":"2018-10-17T08:26:07","slug":"docker-for-mac-with-kubernetes-support","status":"publish","type":"post","link":"https:\/\/www.appservgrid.com\/paw93\/index.php\/2018\/10\/16\/docker-for-mac-with-kubernetes-support\/","title":{"rendered":"Docker for Mac with Kubernetes support"},"content":{"rendered":"

Jan 29, 2018<\/p>\n

by Catalin Jora<\/a><\/p>\n

During DockerCon Copenhagen<\/a>, Docker announced support and integration for Kubernetes, alongside Swarm. The first integration is in the Docker for Mac, where you can run now a 1 node Kubernetes cluster. This allows you to deploy apps with Docker-compose files to that local Kubernetes cluster via the docker cli. In this blogpost, I\u2019ll cover what you need to know about this integration and how to make the most out of it.<\/p>\n

While a lot of computing workload moves to the cloud, the local environment is still relevant. This is the first place where software is built, executed and where (unit) tests run. Docker, helped us to get rid of the famous \u201cit works on my machine\u201d by automating the repetitive and error-prone tasks. But unless you\u2019re into building \u201chello world\u201d apps, you\u2019ll have to manage the lifecycle of a bunch of containers that need to work together. Thus, you\u2019ll need management for your running containers, commonly called nowadays orchestration.<\/p>\n

All major software orchestration platforms have their own \u201cmini\u201d distribution that can run on a developer machine. If you work with Mesos you have minimesos<\/a> (container based), for Kubernetes there is minikube<\/a> (virtual machine). RedHat offers both a virtual machine (minishift<\/a>) and a container based tool (oc<\/a> cli) for their K8s distribution (Openshift). Docker has compose<\/a>, swarm-mode<\/a> orchestration and since recently also supports Kubernetes<\/a> (for now only in Docker for Mac).<\/p>\n

If you\u2019re new to Kubernetes you\u2019ll wanna familiarize with the basic concepts using this official Kubernetes tutorial<\/a> we build together with Google, Remembertoplay<\/a> and Katacoda<\/a>.<\/p>\n

Enabling Kubernetes in Docker for Mac, will install a containerized distribution of Kubernetes and it\u2019s cli (kubectl<\/a>), which will allow you to interact with the cluster. On resource level, the new cluster will use whatever Docker for Mac has available for use.<\/p>\n

The release is in beta (at the time of writing the article) and available via the Docker Edge channel. Once you\u2019re logged in with your Docker account, you can enable Kubernetes via the dedicated menu from the UI:<\/p>\n

\"kubernetes<\/a><\/p>\n

At this point, if you never connected to a Kubernetes cluster on your Mac, you\u2019re good to go. Kubectl will point to the new (and only) configured cluster. If this is not the case, you\u2019ll need to point kubectl to the right cluster. Docker for Mac will not change your default Kubernetes context. You\u2019ll need to manually switch the context to \u2018docker-for-desktop\u2019:<\/p>\n\n\n\n
<\/td>\nkubectl config get-contexts<\/p>\n

CURRENT NAME CLUSTER AUTHINFO NAMESPACE<\/p>\n

…<\/p>\n

docker-for-desktop docker-for-desktop-cluster docker-for-desktop<\/p>\n

* minikube minikube minikube<\/p>\n

…<\/p>\n

kubectl config use-context docker-for-desktop<\/p>\n

Switched to context “docker-for-desktop”.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

Going to kubectl utility now, you should be able to run commands towards the new cluster:<\/p>\n\n\n\n
<\/td>\nkubectl cluster-info<\/p>\n

Kubernetes master is running at https:\/\/localhost:6443<\/p>\n

KubeDNS is running at https:\/\/localhost:6443\/api\/v1\/namespaces\/kube-system\/services\/kube-dns\/proxy<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

Note: You may have already another kubectl installed on your machine (E.g. installed via gcloud utility if you used GKE before, or as a stand-alone program if you used minikube). Docker will install automatically a new kubectl binary in \/usr\/local\/bin\/. You\u2019ll need to decide which one you\u2019ll keep.<\/em><\/p>\n

Ok, let\u2019s try to install our first apps using a Docker-compose file. Yes, the previous sentence is correct. If you want to deploy apps to your new local Kubernetes cluster using the docker cli, docker-compose file is the only way. If you already have some Kubernetes manifests you plan to deploy, you can do it using the known way, with kubectl.<\/p>\n

We\u2019re using here the demo-app from the official docker-page about Kubernetes:<\/p>\n\n\n\n
<\/td>\nwget https:\/\/raw.githubusercontent.com\/jocatalin\/k8s-docker-mac\/master\/docker-compose.yaml<\/p>\n

docker stack deploy -c docker-compose.yaml hello-k8s-from-docker<\/p>\n

Stack hello-k8s-from-docker was updated<\/p>\n

Waiting for the stack to be stable and running…<\/p>\n

– Service db has one container running<\/p>\n

– Service words has one container running<\/p>\n

– Service web has one container running<\/p>\n

Stack hello-k8s-from-docker is stable and running<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

If you\u2019re familiar with Docker swarm, there is nothing new about the command. What\u2019s different is that the stack was deployed to our new Kubernetes cluster. The command generated deployments, replica sets, pods and services for the 3 applications defined in the compose file:<\/p>\n\n\n\n
 <\/p>\n

1<\/p>\n

2<\/p>\n

3<\/p>\n

4<\/p>\n

5<\/p>\n

6<\/p>\n

7<\/p>\n

8<\/p>\n

9<\/p>\n

10<\/p>\n

11<\/p>\n

12<\/p>\n

13<\/p>\n

14<\/p>\n

15<\/p>\n

16<\/p>\n

17<\/p>\n

18<\/p>\n

19<\/p>\n

20<\/p>\n

 <\/td>\n

kubectl get all<\/p>\n

NAME DESIRED CURRENT UP-TO-DATE AVAILABLE AGE<\/p>\n

deploy\/db 1 1 1 1 39s<\/p>\n

deploy\/web 1 1 1 1 39s<\/p>\n

deploy\/words 1 1 1 1 39s<\/p>\n

NAME DESIRED CURRENT READY AGE<\/p>\n

rs\/db-794c8bc8d9 1 1 1 39s<\/p>\n

rs\/web-54cbf7d7fb 1 1 1 39s<\/p>\n

rs\/words-575cd67dff 1 1 1 39s<\/p>\n

NAME READY STATUS RESTARTS AGE<\/p>\n

po\/db-794c8bc8d9-mrw79 1\/1 Running 0 39s<\/p>\n

po\/web-54cbf7d7fb-mx4c7 1\/1 Running 0 39s<\/p>\n

po\/words-575cd67dff-ddgw2 1\/1 Running 0 39s<\/p>\n

NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE<\/p>\n

svc\/db ClusterIP None 55555\/TCP 39s<\/p>\n

svc\/web LoadBalancer 10.96.17.42 80:31420\/TCP 39s<\/p>\n

svc\/words ClusterIP None 55555\/TCP 39s<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

Doing any change in the docker-compose file and re-deploying it (e.g. change the number of replicas, change the image version) will update the Kubernetes app accordingly. The concept of namespaces is supported as well via the –namespace parameter. Deleting the application stacks can also be done via the docker cli.<\/p>\n

Will Docker for Mac allow you to deploy with the docker cli the compose-files on other Kubernetes cluster? No, it won\u2019t. Trying to deploy the same file on another cluster will return this error:<\/p>\n\n\n\n
<\/td>\ncould not find compose.docker.com api.<\/p>\n

Install it on your cluster first<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

The integration is implemented at API level. Open a proxy to the Docker for mac Kubernetes cluster:<\/p>\n\n\n\n
<\/td>\nkubectl proxy<\/p>\n

Starting to serve on 127.0.0.1:8001<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

Going in the browser to http:\/\/localhost:8001<\/a> will reveal some new API\u2019s that are (most probably) responsible for this compose to k8s manifest translation:<\/p>\n\n\n\n
<\/td>\n“\/apis\/compose.docker.com”<\/p>\n

“\/apis\/compose.docker.com\/v1beta1”<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

So at this point, if you want to deploy the same application stack on other clusters, you need to use something like Kompose to convert docker-compose files to Kubernetes manifests (it didn\u2019t work for my example), or write the manifests by hand.<\/p>\n

There are a few advantages here if we\u2019re comparing this implementation with minikube:<\/p>\n