Kubernetes uses cri-o nowadays. If you’re using kubernetes with the intent of exposing your docker sockets to your workloads, that’s just asking for all sorts of fun, hard to debug trouble. It’s best to not tie yourself to your k8s clusters underlying implementation, you just get a lot more portability since most cloud providers won’t even let you do that if you’re managed.

If you want something more akin to how kubernetes does it, there’s always nerdctl on top of the containerd interface. However nerdctl isn’t really intended to be used as anything other than a debug tool for the containerd maintainers.

Not to mention podman can just launch kubernetes workloads locally a.la. docker compose now.

Try using an alternative dns. Some isps DNS servers don’t know how to direct a .zip tld

The thing is though, the instance your create a community from only really affects who you interact with to recover your moderation team if everyone goes poof. Otherwise the instance essentially serves as a vanity domain for the community (think email). It doesn’t matter if lemmy.world is down to me at all. I can still post to its cats community using my sh.itjust.works account just fine. Anyone that isn’t on beehaw will see my posts with or without the origin instance of the community being online (because beehaw is defederated with my instance).