-
Notifications
You must be signed in to change notification settings - Fork 5.6k
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
Installing extensions at system level (user: root
, built-in location) throws an error
#7042
Open
2 tasks done
Comments
benz0li
added
bug
Something isn't working
triage
This issue needs to be triaged by a maintainer
labels
Oct 19, 2024
benz0li
changed the title
Installing extensions at system level (built-in location) throws an error
Installing extensions at *system level* (built-in location) throws an error
Oct 19, 2024
benz0li
changed the title
Installing extensions at *system level* (built-in location) throws an error
Installing extensions at system level (built-in location) throws an error
Oct 19, 2024
benz0li
changed the title
Installing extensions at system level (built-in location) throws an error
Installing extensions at system level (user: Oct 19, 2024
root
, built-in location) throws an error
Installing extensions using the GUI seem to work fine at user level (user:
|
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is there an existing issue for this?
OS/Web Information
code-server --version
: 4.94.2-rc.1 dd2e9fc with Code 1.94.2Steps to Reproduce
Start container:
Install extension:
Expected
Actual
Logs
See above.
Screenshot/Video
-
Does this bug reproduce in native VS Code?
This cannot be tested in native VS Code
Does this bug reproduce in GitHub Codespaces?
This cannot be tested in GitHub Codespaces
Are you accessing code-server over a secure context?
Notes
It seems to work at user level (user:
root
) by executingcode-server --install-extension ms-python.python
, butls -al ~/.local/share/code-server/extensions
revealswhich does not look fine.
FYI @code-asher
The text was updated successfully, but these errors were encountered: