DevPod Kubernetes provider not handling bind mounts correctly

[nesta219]

What happened?
I wanted to use devcontainer mounts to mount a pip.conf file to my DevPod container in order to pull private python dependencies. When I looked at the file on my DevPod's filesystem though, the pip.conf file was not a file, it was an empty directory.

What did you expect to happen instead?
I expected the pip.conf file to be created in the target location

How can we reproduce the bug? (as minimally and precisely as possible)

My devcontainer.json:

{
   ...
  "mounts": [
    {
      "source": "/opt/homebrew/etc/pip.conf",
      "target": "/tmp/pip.conf",
      "type": "bind"
    }
  ],
  ...
}

Local Environment:

• DevPod Version: v0.5.4
• Operating System: mac
• ARCH of the OS: ARM64

DevPod Provider:

• Cloud Provider: aws EKS
• Kubernetes Provider: v1.28.4
• Local/remote provider: ssh

Anything else we need to know?

[pascalbreuninger]

Hey @nesta219,
I've been investigating this for a bit and haven't found a (quick) reliable solution for the kubernetes provider. The problem is that an empty volume mount will be usually (depends on the container runtime) created as a directory in the container.

There are ways around this but none of the ones I'm aware of are easy.
I'd keep this ticket open for now and see how many other people face this problem.