[moondev]

Just like KIND runs containerd inside docker, you can also run dockerd inside containerd backed pods.

Start a privileged pod with the dind image, copy or mount your compose.yaml inside and you should be able to docker compose up and down, all without mounting a socket (that won't exist anyway on containerd CRI nodes)

To go even further, kubevirt runs on kind, launch a VM with your compose file passed in via cloud-init.

[sandGorgon]

this is OpenClaw's docker compose yml - https://github.com/openclaw/openclaw/blob/main/docker-compos... . Arguably the hottest thing in the world right now. Mac Minis are out of stock because of this.

At no point, have I invented a new/better method. Perhaps your way is better.

I just recognise that Docker Compose is loved by most open source developers. And invariably any project you touch will have a docker compose setup by default. And it isnt going away, no matter hard anyone tries to kill. Some things are just too well designed. Docker Compose is one of those things.

I'm just making it possible to run those on kubernetes seamlessly.