You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What happened?
When using a Docker-out-of-Docker (DooD) devcontainer configuration on Windows with WSL2, I'm getting a mount path error. The error occurs because DevPod is using Windows-style paths instead of WSL2-compatible paths.
Error message:
[18:05:56] info docker: Error response from daemon: invalid mount config for type "bind": invalid mount path: 'C:/Users/Flo/.devpod/agent/contexts/default/workspaces/srl-snmp-framework-lab/content' mount path must be absolute.
What did you expect to happen instead?
The path should be automatically converted to WSL2 format (e.g., /mnt/c/Users/Flo/.devpod/agent/contexts/default/workspaces/srl-snmp-framework-lab/) when DevPod interfaces with the Docker daemon running in WSL2.
How can we reproduce the bug? (as minimally and precisely as possible)
Set up Windows with WSL2 install Docker and expose it
What happened?
When using a Docker-out-of-Docker (DooD) devcontainer configuration on Windows with WSL2, I'm getting a mount path error. The error occurs because DevPod is using Windows-style paths instead of WSL2-compatible paths.
Error message:
What did you expect to happen instead?
The path should be automatically converted to WSL2 format (e.g., /mnt/c/Users/Flo/.devpod/agent/contexts/default/workspaces/srl-snmp-framework-lab/) when DevPod interfaces with the Docker daemon running in WSL2.
How can we reproduce the bug? (as minimally and precisely as possible)
My
devcontainer.json
:Local Environment:
DevPod Provider:
Anything else we need to know?
The text was updated successfully, but these errors were encountered: