devcontainer.json not found on disallowed WSL UNC paths #9302

rjra100 · 2023-12-13T13:33:51Z

Type: Bug

Attempting to do "Open Folder in Container" on Dev Containers 0.327.0 on a folder with an existing dev container configuration file appears to get confused:
Dev Container configuration '.devcontainer/devcontainer.json' file already exists.
The dialog offers options "cancel" (which does what it says) or "continue" (which ignores the supplied configuration and tries to ask me to select a configuration template).
In case it matters, the folder I'm opening is in a WSL filesystem (opening via a path like \\wsl$\Ubuntu-20.04\home\<me>\...\<folder>).

On extension version 0.321.0, this opened fine. Reopening the folder (in container) via the recents list works fine with either version.

Expected behaviour would be to use the supplied configuration rather than complaining about its existence and ignoring it. Could you investigate please?

Extension version: 0.327.0
VS Code version: Code 1.85.0 (af28b32d7e553898b2a91af498b1fb666fdebe0c, 2023-12-06T20:48:09.019Z)
OS version: Windows_NT x64 10.0.19044
Modes:
Remote OS version: Linux x64 5.10.16.3-microsoft-standard-WSL2
Remote OS version: Linux x64 5.10.16.3-microsoft-standard-WSL2
Remote OS version: Linux x64 5.10.16.3-microsoft-standard-WSL2

System Info

Item	Value
CPUs	Intel(R) Core(TM) i9-10980XE CPU @ 3.00GHz (36 x 3000)
GPU Status	2d_canvas: enabled canvas_oop_rasterization: enabled_on direct_rendering_display_compositor: disabled_off_ok gpu_compositing: enabled multiple_raster_threads: enabled_on opengl: enabled_on rasterization: enabled raw_draw: disabled_off_ok video_decode: enabled video_encode: enabled vulkan: disabled_off webgl: enabled webgl2: enabled webgpu: enabled
Load (avg)	undefined
Memory (System)	127.80GB (9.16GB free)
Process Argv	--folder-uri vscode-remote://dev-container%2B7b22686f737450617468223a225c5c5c5c77736c245c5c5562756e74752d32302e30345c5c686f6d655c5c72616c6578616e64657237325c5c6769745c5c77735c5c6578706572696d656e74222c226c6f63616c446f636b6572223a66616c73652c22636f6e66696746696c65223a7b22246d6964223a312c2270617468223a222f686f6d652f72616c6578616e64657237322f6769742f77732f6578706572696d656e742f2e646576636f6e7461696e65722f646576636f6e7461696e65722e6a736f6e222c22736368656d65223a227673636f64652d66696c65486f7374227d7d/workspaces/experiment
Screen Reader	no
VM	0%

Item	Value
Remote	Dev Container: experiment-dev
OS	Linux x64 5.10.16.3-microsoft-standard-WSL2
CPUs	Intel(R) Core(TM) i9-10980XE CPU @ 3.00GHz (36 x 2999)
Memory (System)	100.44GB (93.47GB free)
VM	0%

Item	Value
Remote	WSL: Ubuntu-20.04
OS	Linux x64 5.10.16.3-microsoft-standard-WSL2
CPUs	Intel(R) Core(TM) i9-10980XE CPU @ 3.00GHz (36 x 2999)
Memory (System)	100.44GB (93.47GB free)
VM	0%

Item	Value
Remote	Dev Container: qev_taproto-dev
OS	Linux x64 5.10.16.3-microsoft-standard-WSL2
CPUs	Intel(R) Core(TM) i9-10980XE CPU @ 3.00GHz (36 x 2999)
Memory (System)	100.44GB (93.47GB free)
VM	0%

The text was updated successfully, but these errors were encountered:

denera · 2023-12-13T15:38:26Z

I'm also experiencing this issue at the moment. Digging into the container log files, I see this:

[6388 ms] Dev Containers 0.327.0 over Remote - SSH 0.107.1 in VS Code 1.85.0 (af28b32d7e553898b2a91af498b1fb666fdebe0c).
[6388 ms] Start: Run: /bin/sh 
[6400 ms] Start: Run in host: echo ~
[6451 ms] /home/adener
[6451 ms] 
[6452 ms] Start: Run in host: id -un
[6505 ms] adener
[6505 ms] 
[6506 ms] Start: Run in host:  (command -v getent >/dev/null 2>&1 && getent passwd 'adener' || grep -E '^adener|^[^:]*:[^:]*:adener:' /etc/passwd || true)
[6558 ms] userEnvProbe: loginInteractiveShell (default)
[6558 ms] userEnvProbe: not found in cache
[6558 ms] userEnvProbe shell: /bin/bash
[6866 ms] userEnvProbe PATHs:
Probe:     '/home/adener/Developer/scripts/git-custom-commands:/home/adener/Developer/dotfiles/.pyenv/plugins/pyenv-virtualenv/shims:/home/adener/Developer/dotfiles/.pyenv/shims:/home/adener/Developer/dotfiles/.pyenv/bin:/usr/local/cuda/bin:/home/adener/.local/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin:/opt/p4v/bin/:/opt/pycharm-community-2020.3.3/bin'
Container: None
[6965 ms] Start: Run: docker version --format {{.Server.APIVersion}}
[7021 ms] 1.43
[7493 ms] Start: Run: tar --no-same-owner -x -f -
[7568 ms] Start: Run: /home/adener/.vscode-server/bin/af28b32d7e553898b2a91af498b1fb666fdebe0c/node /home/adener/.vscode-remote-containers/dist/dev-containers-cli-0.327.0/dist/spec-node/devContainersSpecCLI.js read-configuration --workspace-folder /home/adener/Developer/code/te-jax-dev --log-level debug --log-format json --config /home/adener/Developer/code/te-jax-dev/.devcontainer/devcontainer.json --include-merged-configuration --mount-workspace-git-root --additional-features {"extensions.verifySignature":false}
[7758 ms] @devcontainers/cli 0.54.1. Node.js v18.15.0. linux 6.2.0-36-generic x64.
[7758 ms] Start: Run: docker ps -q -a --filter label=devcontainer.local_folder=/home/adener/Developer/code/te-jax-dev --filter label=devcontainer.config_file=/home/adener/Developer/code/te-jax-dev/.devcontainer/devcontainer.json
[7779 ms] Start: Run: docker ps -q -a --filter label=devcontainer.local_folder=/home/adener/Developer/code/te-jax-dev
[7794 ms] Resolving Feature dependencies for 'extensions.verifySignature'...
[7795 ms] * Processing feature: extensions.verifySignature
[7795 ms] Legacy feature 'extensions.verifySignature' not supported. Please check https://containers.dev/features for replacements.
[7797 ms] Error: Legacy feature 'extensions.verifySignature' not supported. Please check https://containers.dev/features for replacements.
    at yJ (/home/adener/.vscode-remote-containers/dist/dev-containers-cli-0.327.0/dist/spec-node/devContainersSpecCLI.js:390:4619)
    at tC (/home/adener/.vscode-remote-containers/dist/dev-containers-cli-0.327.0/dist/spec-node/devContainersSpecCLI.js:390:6575)
    at Q (/home/adener/.vscode-remote-containers/dist/dev-containers-cli-0.327.0/dist/spec-node/devContainersSpecCLI.js:390:1751)
    at q7 (/home/adener/.vscode-remote-containers/dist/dev-containers-cli-0.327.0/dist/spec-node/devContainersSpecCLI.js:285:24126)
    at AC (/home/adener/.vscode-remote-containers/dist/dev-containers-cli-0.327.0/dist/spec-node/devContainersSpecCLI.js:285:26717)
    at Su (/home/adener/.vscode-remote-containers/dist/dev-containers-cli-0.327.0/dist/spec-node/devContainersSpecCLI.js:285:26943)
    at vu (/home/adener/.vscode-remote-containers/dist/dev-containers-cli-0.327.0/dist/spec-node/devContainersSpecCLI.js:390:1824)
    at async _eA (/home/adener/.vscode-remote-containers/dist/dev-containers-cli-0.327.0/dist/spec-node/devContainersSpecCLI.js:612:35175)
[7779 ms] Exit code 1

It looks like Dev Containers extension attempts to launch with a --additional-features {"extensions.verifySignature":false} feature, which is no longer supported and errors out.

My devcontainer.json is very barebones because it uses a compose file:

{
    "name": "TE-JAX Development",
    "dockerComposeFile": [ "/home/adener/Developer/containers/docker-compose.yaml" ],
    "service": "te-jax-dev",
    "overrideCommand": false,
    "workspaceFolder": "/home/adener/Developer/code/te-jax-dev"
}

There's nothing in here that has anything to do with the {"extensions.VerifySignature": false} option. I also don't have that in my settings.json either. It appears to be hard-coded into Dev Containers, with no way to control/disable/override in the settings.

I'm wondering if Dev Containers could be mistaking this as an error from the devcontainers.json file, refusing to use what it sees as a faulty configuration, and instead asking the user to select a different container from its preconfigured options.

AidanTweedy · 2023-12-13T18:13:04Z

I just ran into this issue myself.

Try adding an "initializeCommand" to devcontainer.json, such as "initializeCommand": "ls"

For some reason, that works.

rjra100 · 2023-12-14T09:52:27Z

Digging into the container log files, I see this ...

Strange - I don't have any references to extensions.VerifySignature in my logs. The tail end of mine (after the userEnvProbe bits) just has

Container: None
[2023-12-14T09:47:23.593Z] Start: Run in Host: docker version --format {{.Server.APIVersion}}
[2023-12-14T09:47:23.698Z] Stop (105 ms): Run in Host: docker version --format {{.Server.APIVersion}}
[2023-12-14T09:47:23.698Z] 1.43
[2023-12-14T09:47:23.699Z] Start: Run in Host: wslpath -w /home/ralexander72/git/ws/qev_taproto
[2023-12-14T09:47:23.713Z] Stop (14 ms): Run in Host: wslpath -w /home/ralexander72/git/ws/qev_taproto
[2023-12-14T09:47:26.825Z] Start: Run in Host: wslpath -w /home/ralexander72/git/ws/qev_taproto/.devcontainer/devcontainer.json
[2023-12-14T09:47:26.833Z] Stop (8 ms): Run in Host: wslpath -w /home/ralexander72/git/ws/qev_taproto/.devcontainer/devcontainer.json

No obvious sign of problems in there at all.

Try adding an "initializeCommand" to devcontainer.json, such as "initializeCommand": "ls"

Doesn't seem to help for me.

rjra100 · 2023-12-14T10:47:03Z

Ah - digging about in other logfiles, I found this in exhost.log:

2023-12-14 09:47:27.859 [error] CodeExpectedError: cannot open file://wsl%24/Ubuntu-20.04/home/ralexander72/git/ws/qev_taproto/.devcontainer/devcontainer.json. Detail: Unable to read file '\\wsl$\Ubuntu-20.04\home\ralexander72\git\ws\qev_taproto\.devcontainer\devcontainer.json' (Unknown (FileSystemError): UNC host 'wsl$' access is not allowed. Please update the 'security.allowedUNCHosts' setting if you want to allow this host.)
    at r.$tryOpenDocument (vscode-file://vscode-app/c:/Users/ralexander72/AppData/Local/Programs/Microsoft%20VS%20Code/resources/app/out/vs/workbench/workbench.desktop.main.js:2163:62448)

Adding "security.allowedUNCHosts": ["wsl$"] to the settings and restarting VSCode (it doesn't seem to take effect immediately) fixes the issue for me. But I assume this isn't an intended change in behaviour, and having to dig about in the logs to figure out what it's complaining about certainly isn't ideal.

tim-helloquickly · 2023-12-14T13:47:45Z

Ran into this today as well on M2 Macbook Pro running ubuntu

RM-Terrell · 2023-12-14T22:36:42Z

Hitting this today also on an M2 Macbook running Sonoma 14.2. Also running extension version v0.327.0.

puls · 2023-12-14T23:47:27Z

I have this problem as well; downgrading VS Code to 1.84.2 while keeping the latest extension version fixed the problem for me.

kisamoto · 2023-12-17T11:06:37Z

Try adding an "initializeCommand" to devcontainer.json, such as "initializeCommand": "ls"

Can confirm, added "initializeCommand": "echo 'Hello World!'" to devcontainer.json resolved the issue for me on both v0.327.0 and v0.328.0

ceberttylertech · 2023-12-17T21:53:54Z

I also recently ran into this issue after updating VS code while using dev containers, but the initializeCommand did not correct the issue for me without fully rebuilding my dev container with a cleared cache.

valerii15298 · 2023-12-18T10:01:05Z

Have the same problem! Adding "initializeCommand": "echo Initialize...." to devcontainer.json fixed the problem

chrmarti · 2023-12-18T16:58:16Z

Moving the discussion for those where adding an initializeCommand works around the issue with the unexpected --additional-features option to #9325. Please provide additional information there. Thanks.

Keeping the discussion on //wsl$/... being broken here.

@bpasero @deepak1556 Did anything change in the UNC path check with the latest release? (Comment mentioning "security.allowedUNCHosts": ["wsl$"] makes it work above: #9302 (comment).)

bpasero · 2023-12-19T04:03:59Z

Nothing changed from what I can tell. If you are accessing UNC paths in VS Code, you have to allow them via the security.allowedUNCHosts setting. This impacts both server and clients.

More info in the security advisory at GHSA-mmfh-4pv3-39hr

deepak1556 · 2023-12-19T08:24:16Z

Yes nothing changed on the path check side, @rjra100 did you only start seeing the UNC host log for wsl with 1.85 or does 1.84 also report it ?

chrmarti · 2023-12-19T10:43:22Z

Can reproduce now. Something in the extension appears to have changed, investigating.

deepak1556 · 2023-12-19T11:01:26Z

@chrmarti one thing that might be related, Node.js worker threads didn't respect the UNC path checks and they were addressed in 1.85, if your extension relies on it then it wouldn't have error seen before but now it will as expected.

chrmarti · 2023-12-20T11:10:13Z

A bug fix in the extension now calls vscode.workspace.findFiles() also with WSL paths to discover devcontainer.json files in subfolders of .devcontainer. Previously we wouldn't discover these when they were on a WSL path.

I can improve the response from the extension for this case, but to get at all devcontainer.json files, we will either need the user to allow these UNC hosts or use Remote-WSL to first connect to WSL and then open the folder from there.

One can also open the UNC path in VS Code locally first and that would ask you if you want to add WSL to the allowed UNC hosts. Maybe the extension could do something similar.

LoLei · 2023-12-20T15:55:01Z

For me the reason was some VPN connection blocking Dockerhub, so this command that's run when reopening in a dev container timed out:

[187212290 ms] Start: Run: docker inspect --type image php:8.0-apache-buster
[187287371 ms] Error fetching image details: connect ETIMEDOUT xxx.xxx.xxx.xxx:443
[187287371 ms] Start: Run: docker pull php:8.0-apache-buster
Error response from daemon: Get "https://registry-1.docker.io/v2/": net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)
[187302882 ms] []
[187302882 ms] Error response from daemon: No such image: php:8.0-apache-buster

[187302882 ms] Command failed: docker inspect --type image php:8.0-apache-buster
[187302892 ms] Exit code 1

Exiting out of the VPN, and verifying that connecting to Dockerhub works, fixed the issue for me.

rsarrazin2 · 2023-12-21T10:04:24Z

Same here, usually starting vscode via code . from a WSL2 Terminal, now getting the error

[error] CodeExpectedError: cannot open file://wsl.localhost/Ubuntu/path/to/.devcontainer/devcontainer.json. Detail: Unable to read file '\\wsl.localhost\Ubuntu\path\to\.devcontainer\devcontainer.json' (Unknown (FileSystemError): UNC host 'wsl.localhost' access is not allowed. Please update the 'security.allowedUNCHosts' setting if you want to allow this host.)
    at r.$tryOpenDocument (vscode-file://vscode-app/c:/Users/user/AppData/Local/Programs/Microsoft%20VS%20Code/resources/app/out/vs/workbench/workbench.desktop.main.js:2163:62448)

Using "Remote Development" extension pack v0.25.0 on vscode 1.85.1.

Setting "security.allowedUNCHosts": ["wsl.localhost", "wsl$"] works neither when set in /C:/Users/user/AppData/Roaming/Code/User/settings.json nor when set in /home/user/.vscode-server/data/Machine/settings.json.

Will update if I can narrow down a bit more.

rsarrazin2 · 2023-12-21T10:11:55Z

Will update if I can narrow down a bit more.

Important fact: After logging into our container registry (where the docker image pointed to in devcontainer.json is hosted), everything worked fine. Important: There was no need to pull anything, the image was already present locally.

I can't find any log at first sight that would hint at what's happening and why being able to connect to the container registry would be required despite the image's already being present.

Edit 1: Colleagues running on native Linux also faced the error message in the title and could also solve by logging into the container registry. I'm not sure this helps here, maybe it's 2 different issues.

rjra100 · 2023-12-21T16:15:26Z

A bug fix in the extension now calls vscode.workspace.findFiles() also with WSL paths to discover devcontainer.json files in subfolders of .devcontainer. Previously we wouldn't discover these when they were on a WSL path.

...and yet the content took effect... :)

I can improve the response from the extension for this case, but to get at all devcontainer.json files, we will either need the user to allow these UNC hosts or use Remote-WSL to first connect to WSL and then open the folder from there.

Yeah, it's not particularly crazy to have it ask to have the UNC path approved; my problem was having to dig about in non-obvious logfiles to find what the problem was! If it could pop up the kind of approval dialog you get when you just open the UNC path directly, that'd be fine. If that's not possible, if it could at least indicate why it can't open the file, that'd help!

One can also open the UNC path in VS Code locally first and that would ask you if you want to add WSL to the allowed UNC hosts. Maybe the extension could do something similar.

Might be worth noting that this is pretty much exactly what I ended up doing, but while the UNC path can be opened once permission is granted, it doesn't seem to allow the extension to have access until VSCode is restarted.

nanoz · 2023-12-21T17:05:09Z

On my end, I had this message because I was missing a .env file, after cloning one of my template repository. Adding the expected .env file in my .devcontainer/ folder fixed the problem.

ulrichSchreiner · 2024-01-02T10:48:52Z

hi,

i have the same problem with linux machine. my .devcontainer/devcontainer.json is a symlink to another location (which is in a trusted folder). creating a real file seems to work now.

is there a setting in vscode for linux which forbids symlinks? it looks like vscode sees the file but cannot use it.

rbuckland · 2024-01-02T22:38:26Z

I just ran into this issue myself.

Try adding an "initializeCommand" to devcontainer.json, such as "initializeCommand": "ls"

For some reason, that works.

This did resolve the issue (added the "initializeCommand" : "ls",

Setup was

VS Code 1.85.1 on Ubuntu 22.04
Dev Containers extension v0.327.0
mono repo, but VSCode opened at a subfolder.

.git
└── ...
docs        # <-- VScode workspace folder open here
└──.devcontainer
   └── devcontainer.json  
tools/containers/doc-tooling
└── Dockerfile

// devcontainer.json
{
	"name": "Document Writing",
	"build": {
		"context": "../../tools/containers/doc-tooling",
		"dockerfile": "../../tools/containers/doc-tooling/Dockerfile"
	},
	"initializeCommand" : "ls",
        ...
}

engelberger · 2024-01-04T12:05:55Z

Same issue here, but the "initializeCommand" to devcontainer.json, such as "initializeCommand": "ls" is not working for me

chrmarti · 2024-01-08T13:45:39Z

Fixing the UNC path issue here by detecting the case and looking up the config files through WSL. Please open separate issues for other problems. Thanks!

chrmarti · 2024-01-09T15:50:53Z

Fix is available in Dev Containers extension 0.330.0-pre-release.

Verification (requires WSL on Windows):

Set up a devcontainer.json in a WSL folder.
- Run WSL: Connect to WSL.
- Open empty folder in WSL.
- Run Dev Containers: Add Dev Container Configuration Files, pick any template.
- Run Remote: Close Remote Connection.
Remove any WSL entry from the "security.allowedUNCHosts" setting. Restart VS Code if there was one.
In the local window: Run Dev Containers: Open Folder in Container and enter the UNC path to the WSL folder.
- E.g.: \\wsl.localhost\Ubuntu\home\chrmarti\devel\smktst.
Verify that the folder is opened in the dev container without any dialogs about the configuration file.

irsyadpage · 2024-01-09T16:42:35Z

Try adding an "initializeCommand" to devcontainer.json, such as "initializeCommand": "ls"

Can confirm, added "initializeCommand": "echo 'Hello World!'" to devcontainer.json resolved the issue for me on both v0.327.0 and v0.328.0

Adding "initializeCommand" is not working for me.

Fix is available in Dev Containers extension 0.330.0-pre-release.

Verification (requires WSL on Windows):

Set up a devcontainer.json in a WSL folder.

Run WSL: Connect to WSL.

Open empty folder in WSL.

Run Dev Containers: Add Dev Container Configuration Files, pick any template.

Run Remote: Close Remote Connection.

Remove any WSL entry from the "security.allowedUNCHosts" setting. Restart VS Code if there was one.

In the local window: Run Dev Containers: Open Folder in Container and enter the UNC path to the WSL folder.

E.g.: \\wsl.localhost\Ubuntu\home\chrmarti\devel\smktst.

Verify that the folder is opened in the dev container without any dialogs about the configuration file.

This fix is still not working for me and my environment is:

Windows 10 x64
VSCode 1.85.1
Dev Containers v0.330.0 (Pre-Release)
Docker Desktop 4.26.1 (131620)

The Dev Containers logs:

[18647 ms] Start: Run: docker version --format {{json .}}
[18810 ms] {"Client":{"CloudIntegration":"v1.0.35+desktop.5","Version":"24.0.7","ApiVersion":"1.43","DefaultAPIVersion":"1.43","GitCommit":"afdd53b","GoVersion":"go1.20.10","Os":"windows","Arch":"amd64","BuildTime":"Thu Oct 26 09:08:44 2023","Context":"default"},"Server":{"Platform":{"Name":"Docker Desktop 4.26.1 (131620)"},"Components":[{"Name":"Engine","Version":"24.0.7","Details":{"ApiVersion":"1.43","Arch":"amd64","BuildTime":"Thu Oct 26 09:08:02 2023","Experimental":"false","GitCommit":"311b9ff","GoVersion":"go1.20.10","KernelVersion":"5.15.133.1-microsoft-standard-WSL2","MinAPIVersion":"1.12","Os":"linux"}},{"Name":"containerd","Version":"1.6.25","Details":{"GitCommit":"d8f198a4ed8892c764191ef7b3b06d8a2eeb5c7f"}},{"Name":"runc","Version":"1.1.10","Details":{"GitCommit":"v1.1.10-0-g18a0cb0"}},{"Name":"docker-init","Version":"0.19.0","Details":{"GitCommit":"de40ad0"}}],"Version":"24.0.7","ApiVersion":"1.43","MinAPIVersion":"1.12","GitCommit":"311b9ff","GoVersion":"go1.20.10","Os":"linux","Arch":"amd64","KernelVersion":"5.15.133.1-microsoft-standard-WSL2","BuildTime":"2023-10-26T09:08:02.000000000+00:00"}}
[18877 ms] Start: Run: C:\Users\Me\AppData\Local\Programs\Microsoft VS Code\Code.exe --ms-enable-electron-run-as-node c:\Users\Me\.vscode\extensions\ms-vscode-remote.remote-containers-0.330.0\dist\spec-node\devContainersSpecCLI.js read-configuration --workspace-folder c:\dev\_____\codes --log-level debug --log-format json --config c:\dev\_____\codes\.devcontainer\devcontainer.json --mount-workspace-git-root --terminal-columns 199 --terminal-rows 15
[19114 ms] @devcontainers/cli 0.55.0. Node.js v18.15.0. win32 10.0.19045 x64.
[19114 ms] Start: Run: git rev-parse --show-cdup
[19173 ms] Start: Run: docker ps -q -a --filter label=devcontainer.local_folder=c:\dev\_____\codes --filter label=devcontainer.config_file=c:\dev\_____\codes\.devcontainer\devcontainer.json
[19315 ms] Start: Run: docker ps -q -a --filter label=devcontainer.local_folder=c:\dev\_____\codes

chrmarti · 2024-01-10T08:01:06Z

@irsyadpage Could you open a new issue with the complete log? Yours might be a different bug. Thanks.

irsyadpage · 2024-01-10T18:36:29Z

@chrmarti Okay, I opened a new issue: #9381.

rzhao271 · 2024-01-25T19:28:20Z

@chrmarti I'm getting the following on my Windows device on the second-last step.
I also didn't have any disallowed WSL UNC paths added during the verification.

chrmarti · 2024-01-26T07:51:48Z

@rzhao271 Could you try with the OS folder picker? (I.e., turn off the simple file dialog in user setting.)

github-actions bot added the containers Issue in vscode-remote containers label Dec 13, 2023

pelesh mentioned this issue Dec 16, 2023

Dev Container configuration file already exists but is not being used ORNL/ReSolve#121

Open

chrmarti mentioned this issue Dec 18, 2023

Additional features config passed to dev container CLI #9325

Closed

chrmarti self-assigned this Dec 18, 2023

chrmarti added the info-needed Issue requires more information from poster label Dec 18, 2023

chrmarti added this to the December / January 2024 milestone Dec 19, 2023

chrmarti added bug Issue identified by VS Code Team member as probable bug and removed info-needed Issue requires more information from poster labels Dec 19, 2023

kojo12228 mentioned this issue Dec 21, 2023

Fix devcontainer dotnet image tag dotnet/interactive#3390

Merged

chrmarti changed the title ~~"Dev Container configuration file already exists" - but is not being used!~~ devcontainer.json not found on disallowed WSL UNC paths Jan 8, 2024

chrmarti closed this as completed Jan 8, 2024

irsyadpage mentioned this issue Jan 10, 2024

Unable to open directory in a container using the supplied devcontainer.json file. #9381

Closed

ynakayama999 mentioned this issue Jan 12, 2024

Dev Container Configuration '.devcontainer/devcontainer.json' file already exists. #9303

Closed

rzhao271 added the verified Verification succeeded label Jan 25, 2024

rzhao271 added verification-steps-needed Steps to verify are needed for verification and removed verified Verification succeeded labels Jan 25, 2024

chrmarti removed the verification-steps-needed Steps to verify are needed for verification label Jan 26, 2024

rzhao271 added the verified Verification succeeded label Jan 26, 2024

jackparsonss mentioned this issue Feb 3, 2024

Devcontainer Fix UAlbertaFSAE/f1tenth#12

Merged

microsoft locked and limited conversation to collaborators Feb 22, 2024

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

devcontainer.json not found on disallowed WSL UNC paths #9302

devcontainer.json not found on disallowed WSL UNC paths #9302

rjra100 commented Dec 13, 2023

denera commented Dec 13, 2023

AidanTweedy commented Dec 13, 2023

rjra100 commented Dec 14, 2023 •

edited

Loading

rjra100 commented Dec 14, 2023

tim-helloquickly commented Dec 14, 2023

RM-Terrell commented Dec 14, 2023

puls commented Dec 14, 2023

kisamoto commented Dec 17, 2023

ceberttylertech commented Dec 17, 2023 •

edited

Loading

valerii15298 commented Dec 18, 2023

chrmarti commented Dec 18, 2023

bpasero commented Dec 19, 2023 •

edited

Loading

deepak1556 commented Dec 19, 2023

chrmarti commented Dec 19, 2023

deepak1556 commented Dec 19, 2023

chrmarti commented Dec 20, 2023

LoLei commented Dec 20, 2023

rsarrazin2 commented Dec 21, 2023

rsarrazin2 commented Dec 21, 2023 •

edited

Loading

rjra100 commented Dec 21, 2023 •

edited

Loading

nanoz commented Dec 21, 2023

ulrichSchreiner commented Jan 2, 2024

rbuckland commented Jan 2, 2024

engelberger commented Jan 4, 2024

chrmarti commented Jan 8, 2024

chrmarti commented Jan 9, 2024

irsyadpage commented Jan 9, 2024 •

edited

Loading

chrmarti commented Jan 10, 2024

irsyadpage commented Jan 10, 2024

rzhao271 commented Jan 25, 2024

chrmarti commented Jan 26, 2024

devcontainer.json not found on disallowed WSL UNC paths #9302

devcontainer.json not found on disallowed WSL UNC paths #9302

Comments

rjra100 commented Dec 13, 2023

denera commented Dec 13, 2023

AidanTweedy commented Dec 13, 2023

rjra100 commented Dec 14, 2023 • edited Loading

rjra100 commented Dec 14, 2023

tim-helloquickly commented Dec 14, 2023

RM-Terrell commented Dec 14, 2023

puls commented Dec 14, 2023

kisamoto commented Dec 17, 2023

ceberttylertech commented Dec 17, 2023 • edited Loading

valerii15298 commented Dec 18, 2023

chrmarti commented Dec 18, 2023

bpasero commented Dec 19, 2023 • edited Loading

deepak1556 commented Dec 19, 2023

chrmarti commented Dec 19, 2023

deepak1556 commented Dec 19, 2023

chrmarti commented Dec 20, 2023

LoLei commented Dec 20, 2023

rsarrazin2 commented Dec 21, 2023

rsarrazin2 commented Dec 21, 2023 • edited Loading

rjra100 commented Dec 21, 2023 • edited Loading

nanoz commented Dec 21, 2023

ulrichSchreiner commented Jan 2, 2024

rbuckland commented Jan 2, 2024

engelberger commented Jan 4, 2024

chrmarti commented Jan 8, 2024

chrmarti commented Jan 9, 2024

irsyadpage commented Jan 9, 2024 • edited Loading

chrmarti commented Jan 10, 2024

irsyadpage commented Jan 10, 2024

rzhao271 commented Jan 25, 2024

chrmarti commented Jan 26, 2024

rjra100 commented Dec 14, 2023 •

edited

Loading

ceberttylertech commented Dec 17, 2023 •

edited

Loading

bpasero commented Dec 19, 2023 •

edited

Loading

rsarrazin2 commented Dec 21, 2023 •

edited

Loading

rjra100 commented Dec 21, 2023 •

edited

Loading

irsyadpage commented Jan 9, 2024 •

edited

Loading