-
Notifications
You must be signed in to change notification settings - Fork 261
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
Snap: Built-in devcontainer CLI path uses old version #5629
Comments
Is there a workaround? I've tried to replace Running PS.: |
@StefanBrand your editor possibly added a newline at the end of the file while you did that, which breaks it. Doing |
Thank you, this worked for me! Let me just make paths absolute and reformat it so it is easier to copy-paste: echo -n '/snap/code/current/usr/share/code/code' > ~/.config/Code/User/globalStorage/ms-vscode-remote.remote-containers/cli-bin/vscode-path
echo -n '/snap/code/current/usr/share/code/resources/app' > ~/.config/Code/User/globalStorage/ms-vscode-remote.remote-containers/cli-bin/vscode-app-root |
Steps to Reproduce:
~/.config/Code/User/globalStorage/ms-vscode-remote.remote-containers/cli-bin/vscode-path
~/.config/Code/User/globalStorage/ms-vscode-remote.remote-containers/cli-bin/vscode-app-root
When VSCode is installed as a snap, there are two paths: A versioned path (such as
/snap/code/75/usr/share/code/code
) and "current" path (/snap/code/current/usr/share/code/code
) which is symlinked to a versioned path. The problem is that the remote container extension seems to capture the versioned path, which eventually disappears as snap updates VSCode (snap seems to keep the current and one previous release by default). These paths are used for - at minimum - driving the devcontainer cli, which means that after snap updates a mismatched version of the cli may be used (or simply no longer exist, which is how I discovered this).The text was updated successfully, but these errors were encountered: