Dev Containers: Installing Extensions not possible - immediately marked as uninstalled and then deleted #9660
Assignees
Labels
*duplicate
Issue identified as a duplicate of another issue(s)
Comments
|
I have the same issue. Over the past couple of weeks, it has been intermittent but is now a consistent problem. The issue seems to stem from the signature verification for certain extensions. I've noticed it for various extensions in the As a temporary workaround, you can try disabling extension signature verification by adding the following setting to your {
"extensions.verifySignature": false
}Below is an example |
|
Related: microsoft/vscode#207813 |
|
@leostewart thanks for the reply, trying but cannot figure out, how this is supposed to be used. should It does not work for me and also the schema does not contain anything about it. As a result I am getting: |
|
As a workaround I found that commenting / removing some of the extesions in the "customizations": {
"vscode": {
"settings": {},
"extensions": [
// "bierner.markdown-mermaid",
// "bpruitt-goddard.mermaid-markdown-syntax-highlighting",
"davidanson.vscode-markdownlint",
"eamodio.gitlens",
"esbenp.prettier-vscode",
"executablebookproject.myst-highlight",
"github.vscode-github-actions",
"github.vscode-pull-request-github",
"mhutchie.git-graph",
"ms-azuretools.vscode-docker",
"ms-python.black-formatter",
"ms-python.flake8",
"ms-python.gather",
"ms-python.isort",
"ms-python.pylint",
"ms-python.python",
"ms-python.vscode-pylance",
"ms-toolsai.jupyter",
"ms-vscode.live-server",
// "takumii.markdowntable",
"visualstudioexptteam.vscodeintellicode",
"yzhang.markdown-all-in-one"
]
}
}
|
|
@pascal456 it's a setting so should be in "settings": {
"extensions.verifySignature": false
} |
|
wow, works. Thank you! anyways, this is weird, especially because there is not real pattern of a functioning set of extensions (activating / deactivating). |
|
Interesting! I am running into the same issue. But I opened an issue in the VScode repo - microsoft/vscode#208043. Just found this. Not sure if I need to close my issue in the other repo. |
|
I am disappointed to report that the above workaround did not work for me. I tried it two ways: And in the workspace file, where I have |
|
/duplicate Please continue discussion in the above issue. |
|
Thanks for creating this issue! We figured it's covering the same as another one we already have. Thus, we closed this one as a duplicate. You can search for similar existing issues. See also our issue reporting guidelines. Happy Coding! |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I found the following related issues, but they were marked as done and closed. Further the solution was explained as a fix in vs code and @sandy081 asked to install the insider build. I guess this solution is not applicable here, since the issues are quite old. Has this problem reoccurred?
Version Information:
Environment configuration for reproducing:
devcontainer.json{ "name": "projectname", // Or use a Dockerfile or Docker Compose file. More info: https://containers.dev/guide/dockerfile "build": { "dockerfile": "Dockerfile", "args": { "PYTHON_VERSION": "3.11-bookworm" } }, // Features to add to the dev container. More info: https://containers.dev/features. "features": { "ghcr.io/devcontainers/features/docker-outside-of-docker": {} }, // Use 'forwardPorts' to make a list of ports inside the container available locally. // "forwardPorts": [6379], // "runArgs": ["--network=host", "--env-file", ".devcontainer/devcontainer.env"], "runArgs": ["--env-file", ".devcontainer/devcontainer.env"], // add GPU support to the container in case the host supports it "hostRequirements": { "gpu": "optional" }, // Use 'postCreateCommand' to run commands after the container is created. "postCreateCommand": "zsh ./.devcontainer/postcreate.sh", // Configure tool-specific properties. "customizations": { "vscode": { "settings": { "black-formatter.importStrategy": "fromEnvironment", "flake8.importStrategy": "fromEnvironment", "isort.importStrategy": "fromEnvironment", "isort.args": ["--settings-file", "pyproject.toml"], "pylint.importStrategy": "fromEnvironment", "terminal.integrated.defaultProfile.linux": "zsh", "[javascript]": { "editor.defaultFormatter": "esbenp.prettier-vscode" }, "[json]": { "editor.defaultFormatter": "esbenp.prettier-vscode" }, "[jsonc]": { "editor.defaultFormatter": "esbenp.prettier-vscode" }, "[python]": { "editor.codeActionsOnSave": { "source.organizeImports": "explicit" }, "editor.defaultFormatter": "ms-python.black-formatter", "editor.formatOnSave": true, "editor.rulers": [88] }, "git.branchProtection": ["main"], "jupyter.notebookFileRoot": "${workspaceFolder}", "notebook.diff.ignoreMetadata": true, "notebook.diff.ignoreOutputs": true, "notebook.formatOnSave.enabled": true, "python.terminal.activateEnvInCurrentTerminal": true, "python.terminal.activateEnvironment": true, "python.testing.pytestEnabled": true, "python.testing.unittestEnabled": false }, "extensions": [ "bierner.markdown-mermaid", "bpruitt-goddard.mermaid-markdown-syntax-highlighting", "eamodio.gitlens", "esbenp.prettier-vscode", "executablebookproject.myst-highlight", "github.vscode-github-actions", "github.vscode-pull-request-github", "mhutchie.git-graph", "ms-azuretools.vscode-docker", "ms-python.black-formatter", "ms-python.flake8", "ms-python.gather", "ms-python.isort", "ms-python.pylint", "ms-python.python", "ms-python.vscode-pylance", "ms-toolsai.jupyter", "ms-vscode.live-server", "takumii.markdowntable", "visualstudioexptteam.vscodeintellicode", "yzhang.markdown-all-in-one" ] } } // Uncomment to connect as root instead. More info: https://aka.ms/dev-containers-non-root. // "remoteUser": "root" }Dockerfilepostcreate.shDoes this issue occur when you try this locally?: only applicable to dev container configurations
Does this issue occur when you try this locally and all extensions are disabled?: when rebuilding a dev container, so none are installed when setting it up
The text was updated successfully, but these errors were encountered: