-
Notifications
You must be signed in to change notification settings - Fork 263
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
cant use "Dev Container: Open folder in Containers" due to unsupported UNC path, when i use podman #8157
Comments
here is a discuss about UNC path, #7978 (comment) but unfortunally, This method does not work on my computer not matter i use wsl2 or windows, dev container cant open the folder in container with podman |
I have the same problem. When I remove this mount, then podman(docker) works. |
but its added automaticully, i have never added this arg. |
Will add a user setting to turn the automatic mounting off. |
Looks like we still need a release for the extension |
Available in Dev Containers 0.287.0-pre-release. |
I tried to do this with the new option
|
The Closing again for verification as this is a different problem. Thanks. |
I can run the same podman containers elsewhere (barring the minor bug I linked above), just not in the UNC path. I'll open a new issue for that. Untagging so someone else can try verifying |
@connor4312 The issue here is with a workspace folder at a non-UNC path. Podman fails on the automatically added mount point for the Wayland socket which is only added when |
Ahh, gotcha! That works. Sorry I misunderstood. |
Steps to Reproduce:
Does this issue occur when you try this locally?: Yes
Does this issue occur when you try this locally and all extensions are disabled?: No
according to the log, dev container will try to mount the wayland-0 of wlsg to container, in which it uses the UNC path but podman dont support that
The text was updated successfully, but these errors were encountered: