-
Notifications
You must be signed in to change notification settings - Fork 292
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
DevPod Kubernetes provider not handling bind mounts correctly #947
Labels
Comments
Hey @nesta219, There are ways around this but none of the ones I'm aware of are easy. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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, thepip.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 thetarget
locationHow can we reproduce the bug? (as minimally and precisely as possible)
My
devcontainer.json
:Local Environment:
v0.5.4
DevPod Provider:
v1.28.4
Anything else we need to know?
The text was updated successfully, but these errors were encountered: