{ switch(e.key) { case 'k': if (e.metaKey || e.ctrlKey) { e.preventDefault(); $el.focus(); open = true; } break; } }" class="flex-grow px-2 bg-transparent text-white placeholder:text-white outline-none" placeholder=Search tabindex=0>
K
Start typing to search…
`; return; } const search = await pagefind.debouncedSearch(query); if (search === null) { return; } else { const resultsLength = search.results.length const resultsData = await Promise.all(search.results.slice(0, 5).map(r => r.data())); const results = resultsData.map((item, index) => ({...item, index: index + 1})); if (query) { searchBarResults.classList.remove("hidden"); } else { searchBarResults.classList.add("hidden"); } let resultsHTML = `
${resultsLength} results
`; resultsHTML += results .map((item) => { return `
${item.meta.title}
…${item.excerpt}…
`; }) .join(""); if (resultsLength > 5) { resultsHTML += `
Show all results
`; } searchBarResults.innerHTML = resultsHTML; } } searchBarInput.addEventListener("input", search); if (window.heap !== undefined) { searchBarResults.addEventListener('click', function (event) { if (event.target.tagName === 'A' && event.target.closest('.link')) { const searchQuery = event.target.getAttribute('data-query'); const resultIndex = event.target.getAttribute('data-index'); const url = new URL(event.target.href); const properties = { docs_search_target_path: url.pathname, docs_search_target_title: event.target.textContent, docs_search_query_text: searchQuery, docs_search_target_index: resultIndex, docs_search_source_path: window.location.pathname, docs_search_source_title: document.title, }; heap.track("Docs - Search - Click - Result Link", properties); } }); } });
Table of contents
Containerization provides an opportunity to move and scale applications toclouds and data centers. Containers effectively guarantee that those applications run thesame way anywhere, allowing you to quickly and easily take advantage of allthese environments. Additionally, as you scale your applications up, you need sometooling to help automate the maintenance of those applications, enable thereplacement of failed containers automatically, and manage the roll-out ofupdates and reconfigurations of those containers during their lifecycle.
Tools to manage, scale, and maintain containerized applications are calledorchestrators. Two of the most popular orchestration tools are Kubernetes andDocker Swarm. Docker Desktop provides development environments for both of theseorchestrators.
The advanced modules teach you how to:
- Set up and use a Kubernetes environment on your development machine
- Set up and use a Swarm environment on your development machine
Docker Desktop sets up Kubernetes for you quickly and easily. Follow the setup and validation instructions appropriate for your operating system:
Mac
From the Docker Dashboard, navigate to Settings, and select the Kubernetes tab.
Select the checkbox labeled Enable Kubernetes, and select Apply & Restart. Docker Desktop automatically sets up Kubernetes for you. You'll know that Kubernetes has been successfully enabled when you see a green light beside 'Kubernetes running' in Settings.
To confirm that Kubernetes is up and running, create a text file called
pod.yamlwith the following content:apiVersion: v1kind: Podmetadata: name: demospec: containers: - name: testpod image: alpine:latest command: ["ping", "8.8.8.8"]This describes a pod with a single container, isolating a simple ping to 8.8.8.8.
In a terminal, navigate to where you created
pod.yamland create your pod:$ kubectl apply -f pod.yamlCheck that your pod is up and running:
$ kubectl get podsYou should see something like:
NAME READY STATUS RESTARTS AGEdemo 1/1 Running 0 4sCheck that you get the logs you'd expect for a ping process:
$ kubectl logs demoYou should see the output of a healthy ping process:
PING 8.8.8.8 (8.8.8.8): 56 data bytes64 bytes from 8.8.8.8: seq=0 ttl=37 time=21.393 ms64 bytes from 8.8.8.8: seq=1 ttl=37 time=15.320 ms64 bytes from 8.8.8.8: seq=2 ttl=37 time=11.111 ms...Finally, tear down your test pod:
$ kubectl delete -f pod.yaml
Windows
From the Docker Dashboard, navigate to Settings, and select the Kubernetes tab.
Select the checkbox labeled Enable Kubernetes, and select Apply & Restart. Docker Desktop automatically sets up Kubernetes for you. You'll know that Kubernetes has been successfully enabled when you see a green light beside 'Kubernetes running' in the Settings menu.
To confirm that Kubernetes is up and running, create a text file called
pod.yamlwith the following content:apiVersion: v1kind: Podmetadata: name: demospec: containers: - name: testpod image: alpine:latest command: ["ping", "8.8.8.8"]This describes a pod with a single container, isolating a simple ping to 8.8.8.8.
In PowerShell, navigate to where you created
pod.yamland create your pod:$ kubectl apply -f pod.yamlCheck that your pod is up and running:
$ kubectl get podsYou should see something like:
NAME READY STATUS RESTARTS AGEdemo 1/1 Running 0 4sCheck that you get the logs you'd expect for a ping process:
$ kubectl logs demoYou should see the output of a healthy ping process:
PING 8.8.8.8 (8.8.8.8): 56 data bytes64 bytes from 8.8.8.8: seq=0 ttl=37 time=21.393 ms64 bytes from 8.8.8.8: seq=1 ttl=37 time=15.320 ms64 bytes from 8.8.8.8: seq=2 ttl=37 time=11.111 ms...Finally, tear down your test pod:
$ kubectl delete -f pod.yaml
Enable Docker Swarm
Docker Desktop runs primarily on Docker Engine, which has everything you need to run a Swarm built in. Follow the setup and validation instructions appropriate for your operating system:
Mac
Open a terminal, and initialize Docker Swarm mode:
$ docker swarm initIf all goes well, you should see a message similar to the following:
Swarm initialized: current node (tjjggogqpnpj2phbfbz8jd5oq) is now a manager.To add a worker to this swarm, run the following command: docker swarm join --token SWMTKN-1-3e0hh0jd5t4yjg209f4g5qpowbsczfahv2dea9a1ay2l8787cf-2h4ly330d0j917ocvzw30j5x9 192.168.65.3:2377To add a manager to this swarm, run 'docker swarm join-token manager' and follow the instructions.Run a simple Docker service that uses an alpine-based filesystem, and isolates a ping to 8.8.8.8:
$ docker service create --name demo alpine:latest ping 8.8.8.8Check that your service created one running container:
$ docker service ps demoYou should see something like:
ID NAME IMAGE NODE DESIRED STATE CURRENT STATE ERROR PORTS463j2s3y4b5o demo.1 alpine:latest docker-desktop Running Running 8 seconds agoCheck that you get the logs you'd expect for a ping process:
$ docker service logs demoYou should see the output of a healthy ping process:
demo.1.463j2s3y4b5o@docker-desktop | PING 8.8.8.8 (8.8.8.8): 56 data bytesdemo.1.463j2s3y4b5o@docker-desktop | 64 bytes from 8.8.8.8: seq=0 ttl=37 time=13.005 msdemo.1.463j2s3y4b5o@docker-desktop | 64 bytes from 8.8.8.8: seq=1 ttl=37 time=13.847 msdemo.1.463j2s3y4b5o@docker-desktop | 64 bytes from 8.8.8.8: seq=2 ttl=37 time=41.296 ms...Finally, tear down your test service:
$ docker service rm demo
Windows
Open a PowerShell, and initialize Docker Swarm mode:
$ docker swarm initIf all goes well, you should see a message similar to the following:
Swarm initialized: current node (tjjggogqpnpj2phbfbz8jd5oq) is now a manager.To add a worker to this swarm, run the following command: docker swarm join --token SWMTKN-1-3e0hh0jd5t4yjg209f4g5qpowbsczfahv2dea9a1ay2l8787cf-2h4ly330d0j917ocvzw30j5x9 192.168.65.3:2377To add a manager to this swarm, run 'docker swarm join-token manager' and follow the instructions.Run a simple Docker service that uses an alpine-based filesystem, and isolates a ping to 8.8.8.8:
$ docker service create --name demo alpine:latest ping 8.8.8.8Check that your service created one running container:
$ docker service ps demoYou should see something like:
ID NAME IMAGE NODE DESIRED STATE CURRENT STATE ERROR PORTS463j2s3y4b5o demo.1 alpine:latest docker-desktop Running Running 8 seconds agoCheck that you get the logs you'd expect for a ping process:
$ docker service logs demoYou should see the output of a healthy ping process:
demo.1.463j2s3y4b5o@docker-desktop | PING 8.8.8.8 (8.8.8.8): 56 data bytesdemo.1.463j2s3y4b5o@docker-desktop | 64 bytes from 8.8.8.8: seq=0 ttl=37 time=13.005 msdemo.1.463j2s3y4b5o@docker-desktop | 64 bytes from 8.8.8.8: seq=1 ttl=37 time=13.847 msdemo.1.463j2s3y4b5o@docker-desktop | 64 bytes from 8.8.8.8: seq=2 ttl=37 time=41.296 ms...Finally, tear down your test service:
$ docker service rm demo
At this point, you've confirmed that you can run simple containerized workloads in Kubernetes and Swarm. The next step is to write a YAML file that describes how to run and manage these containers.
- Deploy to Kubernetes
- Deploy to Swarm
CLI references
Further documentation for all CLI commands used in this article are available here:
kubectl applykubectl getkubectl logskubectl delete- docker swarm init
- docker service *
