-
Notifications
You must be signed in to change notification settings - Fork 448
rust: Fails since Rust 1.87.0 (2025-05-15) #1361
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
Comments
Rust 1.87.0 and later have removed the long-deprecated RLS and rust-analysis components. This change updates the install script to only add rust-src, rustfmt, and clippy, preventing build errors during feature installation. See: rust-lang/rust#126856 https://blog.rust-lang.org/2022/07/01/RLS-deprecation/ https://github.com/rust-lang/rustup/blob/a92432fc8b6d5d4e56ebd08ca1c45b7b1294c1bd/doc/user-guide/src/concepts/components.md#previous-components Fixes: devcontainers#1361
I can second this. I was about to post an issue myself when I first saw this This is my error log when trying to add the devcontainer feature to a python based devcontainer
I would recommend adding Sources: |
I don't think this is necessary. VSCode downloads and uses its own copy of rust-analyzer. Not sure if enough people use emacs/neovim in a devcontainer/Codespaces to justify installing it using rustup as well. (I mean, not that I really care… but if I were to add it I'd like to understand why I'm doing it.) |
Just ran into this as well. I also think that most tools either install it themselves or don't use it. Complete removal is fine for me. Another option would be to add a |
Rust 1.87.0 has finally removed the long deprecated RLS (see also Previous Components), but the
rust
feature unfortunately installs that component unconditionally:features/src/rust/install.sh
Line 206 in 4f8a62a
This results in a build error:
and "This codespace is currently running in recovery mode due to a container error."
Can we please drop
rls
andrust-analysis
from therustup component add
invocation?The text was updated successfully, but these errors were encountered: