Issues with Kubernetes provider; rebuilds? commands?

[IngwiePhoenix]

Hello!

I am a big fan of using DevContainers to put together my development environment and bring it wherever I go - it has helped me a lot, especially at my work. The place is mainly a sysadmin place, so their setup for devs is... problematic - because it is nonexistent. x) We do have a cluster of k3s nodes, and I want to use that to host my dev environment, because the laptop they gave me is, frankly speaking, shit.

So when I did my initial test trying to launch my app in devpod on our kubernetes cluster, it did build the image successfuly! However, I use dinit as my init system (RUN ["/sbin/dinit", "-o"]) to start up my database and related tools. In my local Podman and even on a remote server's Docker, this works well using VSCode's extensions (Remote - SSH and DevContainers). But when I build the image with DevPod, I run into a multitude of issues:

1. devpod ssh fails as it can not forward the ports and just implodes immediately.
2. When I use devpod up, the dinit -o is not PID1. Not a big problem, but a bit of an annoyance since its configured to send all child processes' output (both stdout and stderr) to the container's console.
3. I might be dumb, but I have not found the CLI command to just straight up attach to a running workspace. o.o

DevPod has the features that I want, but I am pretty sure it's a layer 8 problem on my end to make it work.

Mind giving me a few pointers how to fix this?

Thank you very much and kind regards,
Ingwie