It's kind of a weird concept to grasp. A Docker container itself runs whatever operating system assigned to it via the "image". An image could be something like say an Nginx web server ready to go or just bare bones Alpine Linux.

So, if you have an application that requires multiple containers (RQ Workers, Nginx, ElasticSearch, Redis, python3 apps, etc) then using Kubernetes allows you to view, edit, create, and manage all of the Docker containers within the application's cluster.

Say you had a service running in one container running something like "python manage.py runserver" and while viewing your Kubernetes cluster in the Lens tool, you see that the service only starts then crashes after 1 minute due to a ram error. You then edit the "deployment template" of that service to allocate more RAM to the container via Lens, hit apply, and it auto relaunches with the required amount of RAM.

This article explains the differences better than I can though https://www.ibm.com/cloud/blog/containers-vs-vms

So Kubernetes is like a VM Hypervisor and Docker is like the guest operating system that holds clients? Or am I misunderstanding what is involved?

[quote=Tdarcos post_id=126210 time=1641419280 user_id=829]
Does this include Kubernetes? I have heard the two work together in some contexts.
[/quote]

Kubernetes wouldn't really be all that useful in the case of a Hugo game. Basically Kubernetes is used to scale resources for things such as deployments to online production environments with zero downtime.

You are right though in the matter of say you were using the "Lens" tool to visualize a Kubernetes cluster; commonly inside of that cluster are indeed Docker containers running.

Does this include Kubernetes? I have heard the two work together in some contexts.

realNC told me how to do it, I just have not had time. So I'll try to take time this week. Won't you join me on this thread?