Decided to sit down and try to learn #kubernetes despite the fact that I don't have any real need for it on my little home server. Still, it's been interesting and - I won't lie - a bit frustrating at times. It's very much like using a chainsaw to butter my bread for my use case, but I had a nice feeling of satisfaction when I succeeded in getting #owncast set up through it. I've had some odd issues with Docker failing to launch certain containers through containerd that I have not been able to figure out, however.
I was putting thought into maybe redoing my server setup with kubernetes but I sincerely worry that I'll run into this same containerd issue with some of my other apps.
@jay podman's a "replacement" for docker. The commands are essentially the same as you can do podman build, podman run, etc., just like docker build, etc. ( https://docs.podman.io/en/latest/Commands.html ) Some have symlinked docker -> podman to get scripts to just work. The "k8s" part is that you can feed a k8s-style yaml file (with some types of resources like pods and volumes) to podman play kube ( https://docs.podman.io/en/v4.2/markdown/podman-play-kube.1.html ) and it'll run the container on the local system (like kubectl apply).
@jay
I always liken it to using a bazooka to kill cockroaches.
Kubernetes is amazingly expensive for most jobs, but when you do find the right job it is just perfect.
Add comment