How to get VSCode Liveshare extension working when running inside VSCode Remote Dev Container
When installing the LiveShare extension in a devContainer instance I get an error.
For example using: https://github.com/microsoft/vscode-remote-try-go/ and then adding the extension to the devcontainer.json file
"extensions": [
"ms-vscode.go",
"ms-vsliveshare.vsliveshare-pack"
]
When I attempt to start a liveshare I see:
Agent terminated with exit code: 0 and signal null: FailFast: Couldn't find a valid ICU package installed on the system. Set the configuration flag System.Globalization.Invariant to true if you want to run with no globalization support.at System.Environment.FailFast(System.String) at System.Globalization.GlobalizationMode.GetGlobalizationInvariantMode() at System.Globalization.GlobalizationMode..cctor() at System.Globalization.CultureData.CreateCultureWithInvariantData() at System.Globalization.CultureData.get_Invariant() at System.Globalization.CultureInfo..cctor() at System.StringComparer..cctor() at System.AppDomain.InitializeCompatibilityFlags() at System.AppDomain.Setup(System.Object)Aborted (core dumped)
So it turns out that this requires the docker images to install icu tools and then things function as expected.
For the golang image I added:
RUN apt update && apt install icu-devtools -y
The rebuild the container and things worked nicely.
One thing to note is that you need to use the alternative sign in flow using a code to signin
- VsCode Remote SSH .vscode-server taking up a lot of space
- ssh in vscode error: Permission denied (publickey,password)
- vscode-remote-ssh does not work with SSH using Azure AD authentication
- VSCode Remote SSH - failed: Error: No route to host
- How to fix VS Code error with Remote-SSH: "the terminal process failed to launch: A native exception occurred during launch (forkpty(3) failed.)."?
- How to save a file in vscode-remote SSH with a non-root user privileges
- Using "Remote SSH" in VSCode on a target machine that only allows inbound SSH connections
- How do I configure a different shell for a VS Code SSH Remote?
- I've already setup the ssh key, but VSCode keeps asking for password
- Prevent VSCode from pulling during devcontainer build
- Git extension disabled in VS code with WSL
- VSCode unwantedly inserts and modifies PHP source code (autocomplete?)
- Remote SSH connection hangs at "Downloading vscode server step" after updating VScode to 1.82.0 version
- Edit files with VS Code ssh tool that require sudo permissions
- VSCode debugger runs Perl scripts in an (almost) empty environment
- Jupyter notebook running in Visual Studio Code cannot import local module, but the same jupyter server can
- VS Code Remote-SSH: The vscode server failed to start SSH
- VSCode doesn't show changes in the file editor
- Is it possible to use VScode as a remote editor for git?
- VSCode remote-container default python interpreter
- How to prevent VSCode from raising XHR error when it tries to download the vscode-server locally?
- VS Code Remote - Can't run 'code' command in WSL Ubuntu 18 or WSL 2 Ubuntu 20 - wrong path
- How to specify port for VSCode server when using Remote - SSH?
- How to change vscode-server directory
- How do you use a different theme in a remote VS Code window
- VScode remote connection error: The process tried to write to a nonexistent pipe
- How to connect VSCode to GCP instances
- SSH Agent Forwarding with Visual Studio Code Remote - SSH extension
- copy text from tmux inside VSCode
- overload or extend a Dev Container configuration file (`devcontainer.json`)