Skip to content
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.

Sign up for GitHub

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

Jump to bottom

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

Closed
alexanderilyin opened this issue Dec 13, 2023 · 19 comments
Closed

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

alexanderilyin opened this issue Dec 13, 2023 · 19 comments
Assignees
@chrmarti
Labels
containers Issue in vscode-remote containers info-needed Issue requires more information from poster

Comments

@alexanderilyin
Copy link

alexanderilyin commented Dec 13, 2023 •
edited
Loading

  • VSCode Version: Version: 1.85.1 (Universal) Commit: 0ee08df0cf4527e40edc9aa28f4b5bd38bbff2b2
  • Local OS Version: macOS 13.6.3 (22G436)
  • Remote OS Version: Ubuntu 22.04.3 LTS
  • Remote Extension/Connection Type: Containers

Logs:

[347397 ms] Start: Run: docker compose version --short
[347418 ms] Error: Command failed: docker compose version --short
    at Wg (/home/myusername/.vscode-remote-containers/dist/dev-containers-cli-0.327.0/dist/spec-node/devContainersSpecCLI.js:460:889)
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
    at async TJ (/home/myusername/.vscode-remote-containers/dist/dev-containers-cli-0.327.0/dist/spec-node/devContainersSpecCLI.js:390:23529)
    at async _eA (/home/myusername/.vscode-remote-containers/dist/dev-containers-cli-0.327.0/dist/spec-node/devContainersSpecCLI.js:612:35354)
[347454 ms] Exit code 1

Steps to Reproduce:

  1. Install Docker
  2. Do NOT install Compose Plugin (https://docs.docker.com/compose/install/linux/#install-using-the-repository)
  3. Configure Dev Container using docker-compose.yml

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

Notes

This would not be a problem if you start project from scratch and create devcontainer.json, cause at some point you would install Compose plugin for docker but when someone will start using project on new machine he will get misleading error message:

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

Other part of the UX problem is that related log is not opened and you have to find it via:

> Dev Containers: Show Container Log

Which is confusing for new users.

Tasks
Beta Give feedback
No tasks being tracked yet.
@github-actions github-actions bot added the containers Issue in vscode-remote containers label Dec 13, 2023
@westsiderz
Copy link

I am using Ubuntu 22.04. I had VSCode installed previously, today it updated itself. I have a .devconatiner file, which I have developed in Windows. Getting the same errors. The config file do work on WIndows.

@GaTechThomas
Copy link

Same. It just stopped working. Killed all dev progress. Trying extension version rollback.

@datasalaryman
Copy link

Is this still ongoing? I'm opening a fresh github repo on a container and I'm experiencing the same issue.

@AzureWolf
Copy link

I'm experiencing the same, specifically on mac. Windows is working smoothly. Just started recently.

@ynakayama999
Copy link

Try this hack. I resolved, anyway.
#9302 (comment)

@AzureWolf
Copy link

Try this hack. I resolved, anyway. #9302 (comment)

Thank you for this, but it did not work for me. However, it made me go down a path where I found the solution that worked for me (on Mac): microsoft/vscode#202096

Hope this helps anyone else!

@jeebb
Copy link

jeebb commented Jan 16, 2024

Not sure why but the latest pre-release version (v0.331) still does not work for me. I downgraded the version to v0.321 and it works well for now. Hope that this info could help.

@BMMevius
Copy link

BMMevius commented Jan 18, 2024 •
edited
Loading

Try this hack. I resolved, anyway. #9302 (comment)

For me this gave me the error that a .env file was missing. It is strange that adding an initializeCommand gives me the actual error.

This is the error log after adding the initializeCommand:

[2024-01-18T13:56:04.767Z] Dev Containers 0.327.0 in VS Code 1.85.1 (0ee08df0cf4527e40edc9aa28f4b5bd38bbff2b2).
[2024-01-18T13:56:04.767Z] Start: Resolving Remote
[2024-01-18T13:56:04.804Z] Setting up container for folder or workspace: /home/thomas/Projects/sorama/src/Applications/Tools/SmartStadium/SmartStadiumFangageDashboard
[2024-01-18T13:56:04.872Z] Start: Check Docker is running
[2024-01-18T13:56:04.872Z] Start: Run: docker version --format {{.Server.APIVersion}}
[2024-01-18T13:56:04.908Z] Stop (36 ms): Run: docker version --format {{.Server.APIVersion}}
[2024-01-18T13:56:04.908Z] Server API version: 1.43
[2024-01-18T13:56:04.908Z] Stop (36 ms): Check Docker is running
[2024-01-18T13:56:04.909Z] Start: Run: docker volume ls -q
[2024-01-18T13:56:04.936Z] Stop (27 ms): Run: docker volume ls -q
[2024-01-18T13:56:04.937Z] Start: Run: docker ps -q -a --filter label=vsch.local.folder=/home/thomas/Projects/sorama/src/Applications/Tools/SmartStadium/SmartStadiumFangageDashboard --filter label=vsch.quality=stable
[2024-01-18T13:56:04.961Z] Stop (24 ms): Run: docker ps -q -a --filter label=vsch.local.folder=/home/thomas/Projects/sorama/src/Applications/Tools/SmartStadium/SmartStadiumFangageDashboard --filter label=vsch.quality=stable
[2024-01-18T13:56:04.962Z] Start: Run: docker ps -q -a --filter label=devcontainer.local_folder=/home/thomas/Projects/sorama/src/Applications/Tools/SmartStadium/SmartStadiumFangageDashboard --filter label=devcontainer.config_file=/home/thomas/Projects/sorama/src/Applications/Tools/SmartStadium/SmartStadiumFangageDashboard/.devcontainer/devcontainer.json
[2024-01-18T13:56:04.989Z] Stop (27 ms): Run: docker ps -q -a --filter label=devcontainer.local_folder=/home/thomas/Projects/sorama/src/Applications/Tools/SmartStadium/SmartStadiumFangageDashboard --filter label=devcontainer.config_file=/home/thomas/Projects/sorama/src/Applications/Tools/SmartStadium/SmartStadiumFangageDashboard/.devcontainer/devcontainer.json
[2024-01-18T13:56:04.989Z] Start: Run: docker ps -q -a --filter label=devcontainer.local_folder=/home/thomas/Projects/sorama/src/Applications/Tools/SmartStadium/SmartStadiumFangageDashboard
[2024-01-18T13:56:05.024Z] Stop (35 ms): Run: docker ps -q -a --filter label=devcontainer.local_folder=/home/thomas/Projects/sorama/src/Applications/Tools/SmartStadium/SmartStadiumFangageDashboard
[2024-01-18T13:56:05.025Z] Start: Run: /opt/visual-studio-code/code --ms-enable-electron-run-as-node /home/thomas/.vscode/extensions/ms-vscode-remote.remote-containers-0.327.0/dist/spec-node/devContainersSpecCLI.js read-configuration --workspace-folder /home/thomas/Projects/sorama/src/Applications/Tools/SmartStadium/SmartStadiumFangageDashboard --id-label devcontainer.local_folder=/home/thomas/Projects/sorama/src/Applications/Tools/SmartStadium/SmartStadiumFangageDashboard --id-label devcontainer.config_file=/home/thomas/Projects/sorama/src/Applications/Tools/SmartStadium/SmartStadiumFangageDashboard/.devcontainer/devcontainer.json --log-level debug --log-format json --config /home/thomas/Projects/sorama/src/Applications/Tools/SmartStadium/SmartStadiumFangageDashboard/.devcontainer/devcontainer.json --mount-workspace-git-root
[2024-01-18T13:56:05.329Z] @devcontainers/cli 0.54.1. Node.js v18.15.0. linux 6.7.0-arch3-1 x64.
[2024-01-18T13:56:05.329Z] Start: Run: docker ps -q -a --filter label=devcontainer.local_folder=/home/thomas/Projects/sorama/src/Applications/Tools/SmartStadium/SmartStadiumFangageDashboard --filter label=devcontainer.config_file=/home/thomas/Projects/sorama/src/Applications/Tools/SmartStadium/SmartStadiumFangageDashboard/.devcontainer/devcontainer.json
[2024-01-18T13:56:05.353Z] Stop (24 ms): Run: docker ps -q -a --filter label=devcontainer.local_folder=/home/thomas/Projects/sorama/src/Applications/Tools/SmartStadium/SmartStadiumFangageDashboard --filter label=devcontainer.config_file=/home/thomas/Projects/sorama/src/Applications/Tools/SmartStadium/SmartStadiumFangageDashboard/.devcontainer/devcontainer.json
[2024-01-18T13:56:05.370Z] Stop (345 ms): Run: /opt/visual-studio-code/code --ms-enable-electron-run-as-node /home/thomas/.vscode/extensions/ms-vscode-remote.remote-containers-0.327.0/dist/spec-node/devContainersSpecCLI.js read-configuration --workspace-folder /home/thomas/Projects/sorama/src/Applications/Tools/SmartStadium/SmartStadiumFangageDashboard --id-label devcontainer.local_folder=/home/thomas/Projects/sorama/src/Applications/Tools/SmartStadium/SmartStadiumFangageDashboard --id-label devcontainer.config_file=/home/thomas/Projects/sorama/src/Applications/Tools/SmartStadium/SmartStadiumFangageDashboard/.devcontainer/devcontainer.json --log-level debug --log-format json --config /home/thomas/Projects/sorama/src/Applications/Tools/SmartStadium/SmartStadiumFangageDashboard/.devcontainer/devcontainer.json --mount-workspace-git-root
[2024-01-18T13:56:05.370Z] Start: Run: /opt/visual-studio-code/code --ms-enable-electron-run-as-node /home/thomas/.vscode/extensions/ms-vscode-remote.remote-containers-0.327.0/dist/spec-node/devContainersSpecCLI.js up --user-data-folder /home/thomas/.config/Code/User/globalStorage/ms-vscode-remote.remote-containers/data --container-session-data-folder /tmp/devcontainers-2dd886e6-c73e-46b9-bee7-06d4cb9fb0de1705586164129 --workspace-folder /home/thomas/Projects/sorama/src/Applications/Tools/SmartStadium/SmartStadiumFangageDashboard --workspace-mount-consistency cached --id-label devcontainer.local_folder=/home/thomas/Projects/sorama/src/Applications/Tools/SmartStadium/SmartStadiumFangageDashboard --id-label devcontainer.config_file=/home/thomas/Projects/sorama/src/Applications/Tools/SmartStadium/SmartStadiumFangageDashboard/.devcontainer/devcontainer.json --log-level debug --log-format json --config /home/thomas/Projects/sorama/src/Applications/Tools/SmartStadium/SmartStadiumFangageDashboard/.devcontainer/devcontainer.json --default-user-env-probe loginInteractiveShell --remove-existing-container --mount type=volume,source=vscode,target=/vscode,external=true --skip-post-create --update-remote-user-uid-default on --mount-workspace-git-root
[2024-01-18T13:56:05.657Z] @devcontainers/cli 0.54.1. Node.js v18.15.0. linux 6.7.0-arch3-1 x64.
[2024-01-18T13:56:05.657Z] Start: Run: docker buildx version
[2024-01-18T13:56:05.785Z] Stop (128 ms): Run: docker buildx version
[2024-01-18T13:56:05.786Z] github.com/docker/buildx 0.12.1 30feaa1a915b869ebc2eea6328624b49facd4bfb
[2024-01-18T13:56:05.786Z]
[2024-01-18T13:56:05.786Z] Start: Resolving Remote
[2024-01-18T13:56:05.794Z] Running the initializeCommand from devcontainer.json...
 
[2024-01-18T13:56:05.795Z] Start: Run: /bin/sh -c ls
[2024-01-18T13:56:05.808Z] azure-pipelines.yml   package.json           run-fangage-dashboard.sh
bunfig.toml      package-lock.json      src
bun.lockb        postcss.config.js      tailwind.config.ts
Dockerfile       public             tsconfig.json
Dockerfile.dockerignore  README.md
next.config.js       run-fangage-dashboard.ps1
[2024-01-18T13:56:05.809Z] Stop (14 ms): Run: /bin/sh -c ls
[2024-01-18T13:56:05.809Z]
[2024-01-18T13:56:05.811Z] Start: Run: docker-compose version --short
[2024-01-18T13:56:05.849Z] Stop (38 ms): Run: docker-compose version --short
[2024-01-18T13:56:05.850Z] Docker Compose version: 2.24.0
[2024-01-18T13:56:05.850Z] Start: Run: docker ps -q -a --filter label=com.docker.compose.project=smartstadium --filter label=com.docker.compose.service=smart-stadium-fangage-dashboard
[2024-01-18T13:56:05.873Z] Stop (23 ms): Run: docker ps -q -a --filter label=com.docker.compose.project=smartstadium --filter label=com.docker.compose.service=smart-stadium-fangage-dashboard
[2024-01-18T13:56:05.874Z] Start: Run: docker inspect --type container d677fbecc5fb
[2024-01-18T13:56:05.898Z] Stop (24 ms): Run: docker inspect --type container d677fbecc5fb
[2024-01-18T13:56:05.899Z] Start: Removing existing container.
[2024-01-18T13:56:05.899Z] Start: Run: docker rm -f d677fbecc5fb2112d49f831b38e8f8c5aad1ce4b3eefa91432313720bde7cbe0
[2024-01-18T13:56:06.474Z] Stop (575 ms): Run: docker rm -f d677fbecc5fb2112d49f831b38e8f8c5aad1ce4b3eefa91432313720bde7cbe0
[2024-01-18T13:56:06.474Z] Stop (575 ms): Removing existing container.
[2024-01-18T13:56:06.476Z] Start: Run: docker-compose -f /home/thomas/Projects/sorama/src/Applications/Tools/SmartStadium/docker-compose.yml -f /home/thomas/Projects/sorama/src/Applications/Tools/SmartStadium/SmartStadiumFangageDashboard/.devcontainer/docker-compose.yml --profile * config
[2024-01-18T13:56:06.555Z] Stop (79 ms): Run: docker-compose -f /home/thomas/Projects/sorama/src/Applications/Tools/SmartStadium/docker-compose.yml -f /home/thomas/Projects/sorama/src/Applications/Tools/SmartStadium/SmartStadiumFangageDashboard/.devcontainer/docker-compose.yml --profile * config
[2024-01-18T13:56:06.555Z]
[2024-01-18T13:56:06.555Z] time="2024-01-18T14:56:06+01:00" level=warning msg="The \"AZURE_STORAGE_KEY\" variable is not set. Defaulting to a blank string."
env file /home/thomas/Projects/sorama/src/Applications/Tools/SmartStadium/.env not found: stat /home/thomas/Projects/sorama/src/Applications/Tools/SmartStadium/.env: no such file or directory
 
[2024-01-18T13:56:06.555Z] Exit code 14
[2024-01-18T13:56:06.558Z] Error: Command failed: docker-compose -f /home/thomas/Projects/sorama/src/Applications/Tools/SmartStadium/docker-compose.yml -f /home/thomas/Projects/sorama/src/Applications/Tools/SmartStadium/SmartStadiumFangageDashboard/.devcontainer/docker-compose.yml --profile * config
[2024-01-18T13:56:06.558Z]     at Wg (/home/thomas/.vscode/extensions/ms-vscode-remote.remote-containers-0.327.0/dist/spec-node/devContainersSpecCLI.js:460:889)
[2024-01-18T13:56:06.558Z]     at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
[2024-01-18T13:56:06.558Z]     at async L$ (/home/thomas/.vscode/extensions/ms-vscode-remote.remote-containers-0.327.0/dist/spec-node/devContainersSpecCLI.js:427:1481)
[2024-01-18T13:56:06.558Z]     at async N$ (/home/thomas/.vscode/extensions/ms-vscode-remote.remote-containers-0.327.0/dist/spec-node/devContainersSpecCLI.js:409:3165)
[2024-01-18T13:56:06.558Z]     at async tAA (/home/thomas/.vscode/extensions/ms-vscode-remote.remote-containers-0.327.0/dist/spec-node/devContainersSpecCLI.js:479:3833)
[2024-01-18T13:56:06.558Z]     at async CC (/home/thomas/.vscode/extensions/ms-vscode-remote.remote-containers-0.327.0/dist/spec-node/devContainersSpecCLI.js:479:4775)
[2024-01-18T13:56:06.559Z]     at async NeA (/home/thomas/.vscode/extensions/ms-vscode-remote.remote-containers-0.327.0/dist/spec-node/devContainersSpecCLI.js:612:11107)
[2024-01-18T13:56:06.559Z]     at async MeA (/home/thomas/.vscode/extensions/ms-vscode-remote.remote-containers-0.327.0/dist/spec-node/devContainersSpecCLI.js:612:10848)
[2024-01-18T13:56:06.575Z] Stop (1205 ms): Run: /opt/visual-studio-code/code --ms-enable-electron-run-as-node /home/thomas/.vscode/extensions/ms-vscode-remote.remote-containers-0.327.0/dist/spec-node/devContainersSpecCLI.js up --user-data-folder /home/thomas/.config/Code/User/globalStorage/ms-vscode-remote.remote-containers/data --container-session-data-folder /tmp/devcontainers-2dd886e6-c73e-46b9-bee7-06d4cb9fb0de1705586164129 --workspace-folder /home/thomas/Projects/sorama/src/Applications/Tools/SmartStadium/SmartStadiumFangageDashboard --workspace-mount-consistency cached --id-label devcontainer.local_folder=/home/thomas/Projects/sorama/src/Applications/Tools/SmartStadium/SmartStadiumFangageDashboard --id-label devcontainer.config_file=/home/thomas/Projects/sorama/src/Applications/Tools/SmartStadium/SmartStadiumFangageDashboard/.devcontainer/devcontainer.json --log-level debug --log-format json --config /home/thomas/Projects/sorama/src/Applications/Tools/SmartStadium/SmartStadiumFangageDashboard/.devcontainer/devcontainer.json --default-user-env-probe loginInteractiveShell --remove-existing-container --mount type=volume,source=vscode,target=/vscode,external=true --skip-post-create --update-remote-user-uid-default on --mount-workspace-git-root
[2024-01-18T13:56:06.575Z] Exit code 1
[2024-01-18T13:56:06.580Z] Command failed: /opt/visual-studio-code/code --ms-enable-electron-run-as-node /home/thomas/.vscode/extensions/ms-vscode-remote.remote-containers-0.327.0/dist/spec-node/devContainersSpecCLI.js up --user-data-folder /home/thomas/.config/Code/User/globalStorage/ms-vscode-remote.remote-containers/data --container-session-data-folder /tmp/devcontainers-2dd886e6-c73e-46b9-bee7-06d4cb9fb0de1705586164129 --workspace-folder /home/thomas/Projects/sorama/src/Applications/Tools/SmartStadium/SmartStadiumFangageDashboard --workspace-mount-consistency cached --id-label devcontainer.local_folder=/home/thomas/Projects/sorama/src/Applications/Tools/SmartStadium/SmartStadiumFangageDashboard --id-label devcontainer.config_file=/home/thomas/Projects/sorama/src/Applications/Tools/SmartStadium/SmartStadiumFangageDashboard/.devcontainer/devcontainer.json --log-level debug --log-format json --config /home/thomas/Projects/sorama/src/Applications/Tools/SmartStadium/SmartStadiumFangageDashboard/.devcontainer/devcontainer.json --default-user-env-probe loginInteractiveShell --remove-existing-container --mount type=volume,source=vscode,target=/vscode,external=true --skip-post-create --update-remote-user-uid-default on --mount-workspace-git-root
[2024-01-18T13:56:06.580Z] Exit code 1

@chrmarti chrmarti self-assigned this Jan 22, 2024
@chrmarti
Copy link
Contributor

The warning dialog (Dev Container Configuration '.devcontainer/devcontainer.json' file already exists.) can have various underlying reasons. I have released a fix that will instead show an error dialog explaining that the config could not be loaded (which is the real reason and wasn't handled properly). The fix should also make the initializeCommand workaround obsolete.

Could everyone seeing this give Dev Containers 0.334.0-pre-release a try and if it still fails post the log output here? Thanks!

@BMMevius Your log shows an issue with a missing env file:

env file /home/thomas/Projects/sorama/src/Applications/Tools/SmartStadium/.env not found: stat /home/thomas/Projects/sorama/src/Applications/Tools/SmartStadium/.env: no such file or directory

@chrmarti chrmarti added the info-needed Issue requires more information from poster label Jan 22, 2024
@Levi-Montgomery
Copy link

Switching to that pre-release version fixed the issue for me.

@ringe
Copy link

ringe commented Jan 24, 2024 •
edited
Loading

Adding a .env file fixed the issue for me.

Version: 1.85.2
Commit: 8b3775030ed1a69b13e4f4c628c612102e30a681
Date: 2024-01-18T06:40:19.222Z
Electron: 25.9.7
ElectronBuildId: 26354273
Chromium: 114.0.5735.289
Node.js: 18.15.0
V8: 11.4.183.29-electron.0
OS: Linux x64 6.5.0-14-generic

@JackCaster
Copy link

I get the same error message
image
but in reality the problem is that the corporate network is blocking the connection. I was quite confused until I realized I needed to deactivate the firewall. The error message was misleading.

2024-01-25 08:48:13.697 [error] CodeExpectedError: cannot open file://wsl.localhost/Ubuntu/home/xxx/dev/accumulate/.devcontainer/devcontainer.json. Detail: Unable to read file '\\wsl.localhost\Ubuntu\home\xxx\dev\accumulate\.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/xxx/AppData/Local/Programs/Microsoft%20VS%20Code/resources/app/out/vs/workbench/workbench.desktop.main.js:2163:62448)

@chrmarti
Copy link
Contributor

@JackCaster Could you open a new issue with the complete log and the steps you took to get there? Thanks!

I should have mentioned: Currently the latest Dev Containers versions need VS Code Insiders. Please make sure you are giving the latest version a try (currently Dev Containers 0.336.0-pre-release).

@jaques-sam
Copy link

jaques-sam commented Jan 28, 2024 •
edited
Loading

Still experiencing the issue, I don't know how to solve this. Adding an .env file nor switching to pre-release helps for me.

EDIT: from the logs I'm seeing this error:

31466621 ms] Error: Failed to download package for ghcr.io/stuartleeks/dev-container-features/shell-history
at Va (/home/sam/.vscode/extensions/ms-vscode-remote.remote-containers-0.327.0/dist/spec-node/devContainersSpecCLI.js:285:18410)
at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
at async gJ (/home/sam/.vscode/extensions/ms-vscode-remote.remote-containers-0.327.0/dist/spec-node/devContainersSpecCLI.js:285:25957)
at async q7 (/home/sam/.vscode/extensions/ms-vscode-remote.remote-containers-0.327.0/dist/spec-node/devContainersSpecCLI.js:285:24454)
at async AC (/home/sam/.vscode/extensions/ms-vscode-remote.remote-containers-0.327.0/dist/spec-node/devContainersSpecCLI.js:285:26711)
at async Su (/home/sam/.vscode/extensions/ms-vscode-remote.remote-containers-0.327.0/dist/spec-node/devContainersSpecCLI.js:285:26937)
at async vu (/home/sam/.vscode/extensions/ms-vscode-remote.remote-containers-0.327.0/dist/spec-node/devContainersSpecCLI.js:390:1818)
at async _eA (/home/sam/.vscode/extensions/ms-vscode-remote.remote-containers-0.327.0/dist/spec-node/devContainersSpecCLI.js:612:35175)
[31466639 ms] Exit code 1

When removing this line, it fixes the issue. So the error we're seeing, the title of this issue, is just very confusing and incorrect!

@jaques-sam
Copy link

Linked to devcontainers/features#221

@chrmarti
Copy link
Contributor

@jaques-sam Make sure to try with VS Code Insiders (https://code.visualstudio.com/insiders/) and the latest pre-release version of Dev Containers (currently 0.338.0). (The current pre-release version only installs with VS Code Insiders, this will change when VS Code 1.86 is released and alongside it a new Dev Containers stable version later this week.)

@pantelis
Copy link

pantelis commented Feb 1, 2024

In Ubuntu 22.04, and VSCode in 1.86.0, switching the devcontainer extension only to pre-release version fixes the issue for me.

@egonbraun
Copy link

In Ubuntu 22.04, and VSCode in 1.86.0, switching the devcontainer extension only to pre-release version fixes the issue for me.

I confirm that on macOS 14.3 (Sonoma) going for the pre-release version also fixed the issue. It has started for me when updating vscode to 1.86.0.

@chrmarti
Copy link
Contributor

chrmarti commented Feb 2, 2024

If you still see this, make sure you have the latest Dev Containers extension version installed. For any remaining problems please open new issues. Thanks!

@chrmarti chrmarti closed this as completed Feb 2, 2024
@microsoft microsoft locked and limited conversation to collaborators Mar 18, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@chrmarti chrmarti

Labels
containers Issue in vscode-remote containers info-needed Issue requires more information from poster
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests