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.

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

Installation of "ms-vscode.wasm-wasi-core" is broken in devcontainers #108

Open
michaelp opened this issue Jul 23, 2023 · 1 comment
Open
Labels
bug Issue identified by VS Code Team member as probable bug
Milestone

Comments

@michaelp
Copy link

Summary:

The extension is installed as disabled

Expected results:

The extension is installed, activated and enabled

Symptoms

This extension is disabled in this workspace because it is defined to run in the Remote Extension Host. Please install the extension in 'Dev Container: sample-dotnet-wasi-vscode' to enable it.

Workaround

Manually install/enable the extension inside the devcontainer.
This is a tedious manual step and a bad user experience in general.

Steps to reproduce:

use devcontainer.json with the following content

{
	"name": "sample-dotnet-wasi-vscode",
	"image": "mcr.microsoft.com/devcontainers/base:bullseye",
	"features": {
		"ghcr.io/devcontainers/features/dotnet:1": {
			"version" : "8.0.100-preview.6.23330.14",
			"installUsingApt": false
		}
    	        ,"ghcr.io/devcontainers/features/node:1": {}
		,"ghcr.io/wxw-matt/devcontainer-features/command_runner:latest": {
			"command1": "wget https://github.com/WebAssembly/wasi-sdk/releases/download/wasi-sdk-20/wasi-sdk_20.0_amd64.deb",
			"command2": "sudo apt install ./wasi-sdk_20.0_amd64.deb",
			"command3": "rm ./wasi-sdk_20.0_amd64.deb"
                }
	}
	,"containerEnv": { "WASI_SDK_PATH": "/opt/wasi-sdk" }
	, "customizations": {
		"vscode": {
			"extensions": [
				"ms-vscode.wasm-wasi-core"
			]
		}
	}
	,"postCreateCommand": "dotnet workload install wasi-experimental"
	,"remoteUser": "vscode"
}

VSCODE version

➜ code --version
1.80.1
74f6148eb9ea00507ec113ec51c489d6ffb4b771
x64 
@dbaeumer
Copy link
Member

This has very likely to do with the fact that the extension runs on the wrong extension host in this setup.

@dbaeumer dbaeumer added the bug Issue identified by VS Code Team member as probable bug label Dec 18, 2024
@dbaeumer dbaeumer added this to the Backlog milestone Dec 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Issue identified by VS Code Team member as probable bug
Projects
None yet
Development

No branches or pull requests

2 participants