[mrfusion]

Why kubertetes vs docker? And why rust vs D or golang ?

[JamesBarney]

My God does Kubernetes sometimes feel like using a cannon to remove a zit.

[hanklazard]

Ha! I realized this yesterday after considering it (very briefly) for a home lab deployment—I’m pretty sure I dodged a cannonball on that one.

[dpacmittal]

Docker-compose with nginx-proxy should work well for home labs.

[giovannibonetti]

You may also use Caddy instead of Ngnix. It's way easier to set up and customize.

[OJFord]

Until it's not just one machine. You might briefly then use Swarm... But does anyone for long, whether production or home?

K8s has its complexities for sure, but to me it's the simplest - or at least 'only figure it out once' way of running multiple machines (besides having 'the webserver', 'the db server' etc., of course.)

[Aeolun]

I feel like there should be a better thing than kubernetes. In theory it’s simple, but in practice it’s so convoluted!

[hanklazard]

Yeah, that’s the plan I went back to when I realized I was way off track!

[NicoJuicy]

I can agree on this :p

[speedplane]

> Why kubertetes vs docker?

Docker is for building a computer program to run on a single computer.

Kubernetes is for building a cluster, often across many computers with many programs.

They work together.

[TallGuyShort]

Kubernetes still almost always uses Docker as the runtime. Docker was late to the party with all the other stuff Kubernetes does. With Amazon, Google and Microsoft all offering managed K8s and Enterprise private cloud offerings too, I don't think unseating K8s as a management plane for cloud-native microservices will be trivial, even if the tech is immature and has valid criticisms.

[pepemon]

Kubernetes and Docker (if we're talking about Docker as CRI, most often this is implicitly assumed) are totally different things.