Devpod automatically fixes workspace file ownership, but the behavior is different under docker-compose and directly using images

[zerodegress]

I've recently been experimenting with using devpod to try out devcontainer (I'm also using rootless' podman to go along with it).
In the course of my work, I found that if the remoteUser setting is set to a “1000:1000” user, devpod does not fix the file permissions on that workspace - in fact, this user is mapped to a “1000:1000” user on my host machine. user on my host.

But this only works if you specify the image directly: when I specify docker-compose to use in the workspace, I find that all file permissions are repaired by devpod to a user like “100999” (and if you force it back to the original permissions, you can't write in the container), which is not the same behavior as before.

Is this due to podman? Or is it a feature of devpod? Or is it some kind of bug?

[zerodegress]

I found that #1665 appeared similar to me: it seems that devpod's call to podman compose mistook podman-compose for a compatible implementation of docker-compose, causing devpod to fall back to a strange fixed behavior
If I use docker-compose instead of podman-compose (while installing the podman-docker compatibility package first), then the behavior is exactly the same, which is exactly what I want.