error: rustup is not installed at '/home/user/.cargo' when $RUSTUP_HOME is set to something other than the former #2886

bbros-dev · 2021-10-30T09:15:15Z

Problem

Rustup cannot update when CARGO_HOME is not the Linux default ~/.cargo
Then rustup self uninstall fails to work
At https://www.rust-lang.org/tools/install, there are no further instructions, or a link to those instructions, on how to uninstall rustup.

Steps

20:02 $ echo $RUSTUP_HOME
/home/<snip>/.rustup
✔ ~/src/<snip> [port ↑·2|✚ 2…1]
20:02 $ echo $CARGO_HOME
/home/<snip>/.local/share/cargo
^[[A✔ ~/src/<snip> [port ↑·2|✚ 2…1]
20:02 $ which rustup
/home/<snip>/.local/share/cargo/bin/rustup
✔ ~/src/<snip> [port ↑·2|✚ 2…1]
20:02 $ rustup self update
error: rustup is not installed at '/home/<snip>/.cargo'

Possible Solution(s)
No idea. We seem to be in a Mexican-standoff.

Notes

Output of rustup --version:

$ rustup --version
rustup 1.23.1 (3df2264a9 2020-11-30)
info: This is the version for the rustup toolchain manager, not the rustc compiler.
info: The currently active `rustc` version is `rustc 1.56.0-nightly (5ad7389bd 2021-08-06)`

Output of rustup show:

20:14 $ rustup show
Default host: x86_64-unknown-linux-gnu
rustup home:  /home/<snip>/.rustup

installed toolchains
--------------------

stable-x86_64-unknown-linux-gnu
nightly-x86_64-unknown-linux-gnu (default)

active toolchain
----------------

nightly-x86_64-unknown-linux-gnu (default)
rustc 1.56.0-nightly (5ad7389bd 2021-08-06)

The text was updated successfully, but these errors were encountered:

kinnison · 2021-11-08T14:38:17Z

Our test suite sets those variables in order to operate, so I'm not sure how this could be happening to you. Can you confirm that CARGO_HOME is definitely exported to subshells? Also how did you install rustup? Did you install in those specific dirs, or did you move the installation later?

rbtcollins · 2021-12-11T17:33:19Z

A month with no response - @bbros-dev please reply or we'll need to close this with insufficient information

kennystrawnmusic · 2021-12-28T19:04:45Z

This happens on my end too — but only if run from a script. Works perfectly fine if run from the shell of any user — and this is if I put export RUSTUP_HOME=/opt/rust and export CARGO_HOME=/opt/rust in the system-wide /etc/bash.bashrc file.

Again, perfectly fine if run from a shell, but if I write something like /usr/bin/rustup-upgrade.sh and add the rustup self update and/or rustup update commands to said script, that’s when this problem is run into — and in that case, even adding source /etc/bash.bashrc to the top of the script in order to ensure that the imports defined in that file also make it into the script makes no difference. This problem likewise also occurs when I try to create something like /lib/systemd/system/rustup-update.timer to automatically run the rustup self update and/or rustup update commands in the background.

Re: @bbros-dev — it would help to add “when $RUSTUP_HOME is set to something other than the former” to the end of this bug report’s title to make this report more clear.

@rbtcollins — might want to remove the “inactive” label per this reproduction.

bbros-dev · 2022-01-26T22:31:58Z

Thanks for taking the time to look at this.
@rbtcollins apologies for the delay - RL.

The following is a complete log of a new shell - @kinnison full setup details follow. You'll note that ~/.rustup does not exist, as expected, but then is created by rustup show, despite RUSTUP_HOME pointing to an existing location.
I expected rustup show to never create or delete anything on the system?
Not sure if this is related or a separate issue?

~$ ls ~/.rustup
ls: cannot access '/home/<user>/.rustup': No such file or directory

~$ echo $RUSTUP_HOME 
/home/<user>/.local/share/rustup

~$ echo $CARGO_HOME 
/home/<user>/.local/share/cargo

~$ rustup show
Default host: x86_64-unknown-linux-gnu
rustup home:  /home/<user>/.rustup

no active toolchain

~$ ls ~/.rustup
settings.toml

~$ RUSTUP_HOME=$RUSTUP_HOME rustup show
Default host: x86_64-unknown-linux-musl
rustup home:  /home/<user>/.local/share/rustup

stable-x86_64-unknown-linux-musl (default)
(error reading rustc version)

~$ ls ~/.local/share/rustup
downloads  settings.toml  tmp  toolchains  update-hashes

Can you confirm that CARGO_HOME is definitely exported to subshells?

Yes, I believe so - see the above details from new bash shell. Setup details follow.

Also how did you install rustup? Did you install in those specific dirs, or did you move the installation later?

Setup is using Chef recipes:

~/.bashrc

#!/usr/bin/env bash

[ -f /etc/skel/.bashrc ] && source /etc/skel/.bashrc

for file in ~/.config/bash/bashrc.d/*.bashrc
do
  test -f "$file" || continue
  test -x "$file" || continue
  # shellcheck source=/dev/null
  source "$file"
done

~/.config/bash/bashrc.d/30-rustup.bashrc

CARGO_HOME=${XDG_DATA_HOME}/cargo
RUSTUP_HOME=${XDG_DATA_HOME}/rustup
PATH="${CARGO_HOME}/bin:${RUSTUP_HOME}/bin:$PATH"

Rustup is installed by the following recipe:

# frozen_string_literal: true

pkgs = %w[
  musl-dev
  musl-tools
  musl
]

pkgs.each do |pkg|
  package pkg do
    action :install
  end
end

node['developer']['users'].each do |usr|
  bash "Create #{usr} Rust install" do
    code <<-EOCODE
    curl https://sh.rustup.rs -sSf | \
      sh -s -- \
            -y \
            --verbose \
            --default-host x86_64-unknown-linux-musl \
            --default-toolchain stable \
            --profile default \
            --no-modify-path
    EOCODE
    creates "/home/#{usr}/.local/share/rustup"
    environment ({ 'CARGO_HOME': "/home/#{usr}/.local/share/cargo",
                   'DISPLAY': ':0',
                   'HOME': "/home/#{usr}",
                   'RUSTUP_HOME': "/home/#{usr}/.local/share/rustup",
                   'USER': usr })
    user        usr
    not_if %([ -d "/home/#{usr}/.local/share/rustup" ])
  end

  link "/home/#{usr}/.local/bin/rustup" do
    to "/home/#{usr}/.local/share/cargo/bin/rustup"
  end

  execute "/home/#{usr}/.local/bin/rustup update --no-self-update stable" do
    environment ({ 'DISPLAY': ':0',
                   'HOME': "/home/#{usr}",
                   'USER': usr,
                   'CARGO_HOME': "/home/#{usr}/.local/share/cargo",
                   'RUSTUP_HOME': "/home/#{usr}/.local/share/rustup" })
    user        usr
  end

  ## Install components
  #
  %w[
    clippy
    rustfmt
    rust-src
  ].each do |c|
    execute "/home/#{usr}/.local/bin/rustup component add #{c}" do
      environment ({ 'DISPLAY': ':0',
                     'HOME': "/home/#{usr}",
                     'USER': usr,
                     'CARGO_HOME': "/home/#{usr}/.local/share/cargo",
                     'RUSTUP_HOME': "/home/#{usr}/.local/share/rustup" })
      user        usr
    end
  end
end

kennystrawnmusic · 2022-01-27T05:56:54Z

To further corroborate what @bbros-dev is saying, here's the full text of /etc/bash.bashrc on my end:

#
# /etc/bash.bashrc
#

# If not running interactively, don't do anything
[[ $- != *i* ]] && return

[[ $DISPLAY ]] && shopt -s checkwinsize

PS1='[\u@\h \W]\$ '

case ${TERM} in
  xterm*|rxvt*|Eterm|aterm|kterm|gnome*)
    PROMPT_COMMAND=${PROMPT_COMMAND:+$PROMPT_COMMAND; }'printf "\033]0;%s@%s:%s\007" "${USER}" "${HOSTNAME%%.*}" "${PWD/#$HOME/\~}"'

    ;;
  screen*)
    PROMPT_COMMAND=${PROMPT_COMMAND:+$PROMPT_COMMAND; }'printf "\033_%s@%s:%s\033\\" "${USER}" "${HOSTNAME%%.*}" "${PWD/#$HOME/\~}"'
    ;;
esac

[ -r /usr/share/bash-completion/bash_completion   ] && . /usr/share/bash-completion/bash_completion

if [ -f /opt/rust/env ]; then
  source /opt/rust/env
fi

export RUSTUP_HOME=/opt/rust
export CARGO_HOME=/opt/rust

alias pacman='sudo pacman --noconfirm'

When I went on to create something like "rustup-update.sh" with the following content:

#!/bin/bash
rustup self update
rustup update

It would fail with this error when I tried to run it.

This, however, seems to have begun working fine a month later on my end for some reason ― not sure why I was able to reproduce this on December 28 but not now.

krishnachittur · 2022-02-04T18:57:00Z

@bbros-dev I think your issue might be in the file ~/.config/bash/bashrc.d/30-rustup.bashrc:

CARGO_HOME=${XDG_DATA_HOME}/cargo
RUSTUP_HOME=${XDG_DATA_HOME}/rustup
PATH="${CARGO_HOME}/bin:${RUSTUP_HOME}/bin:$PATH"

Bash doesn't export these variables to subshells, which is resulting in your problem where rustup isn't seeing $CARGO_HOME. (I made this same mistake myself today, except in fish, by writing set -U CARGO_HOME blah instead of set -Ux CARGO_HOME blah.) To fix it, use the export keyword to tell bash to export these environment variables to subshells, like this:

export CARGO_HOME=${XDG_DATA_HOME}/cargo
export RUSTUP_HOME=${XDG_DATA_HOME}/rustup
export PATH="${CARGO_HOME}/bin:${RUSTUP_HOME}/bin:$PATH"

bbros-dev · 2022-03-10T04:49:53Z

@krishnachittur, thank you that does appear to have resolved the error. IIUC then the issue is as follows:

Given the folder `~/.rustup` does not exist
  And the environment variable RUSTUP_HOME is not set
 When a user runs `rustup self update`
 Then the stderr output does not contain:
"""
error: rustup is not installed at '/home/<snip>/.cargo'
"""
  And the stderr output does contain:
"""
error: rustup is not installed at '/home/<snip>/.rustup' and RUSTUP_HOME is not set.  One is required.
"""

Does that sound correct?

krishnachittur · 2022-03-10T05:34:48Z

@bbros-dev In other words, you think the current error message is unclear? That seems like a reasonable complaint to me. Might be an easy PR as well.

danieleades · 2024-02-28T17:04:28Z

i'm running into this trying to get caching to work properly in gitlab CI. A quick search shows i'm not the only one getting stumped here

default:
  image: "rust:latest"

variables:
  CARGO_HOME: ${CI_PROJECT_DIR}/.cargo # Move cargo data into the project directory so it can be cached

cache:
  key: ${CI_COMMIT_REF_SLUG} # Share cache between all jobs on one branch/tag
  paths:
    - .cargo/bin
    - .cargo/registry/index
    - .cargo/registry/cache
    - target/debug/deps
    - target/debug/build
  policy: pull-push

before_script:
  - rustup update
  - rustup install stable

# ...

rustup update fails with "error: rustup is not installed at ..."

kinnison · 2024-02-29T09:16:39Z

@danieleades I suggest you try out https://gitlab.com/rust-ci/rust-ci - I know the authors of that and they're pretty helpful.

danieleades · 2024-02-29T11:33:17Z

see https://gitlab.com/rust-ci/rust-ci/-/issues/39

Xenira · 2024-06-24T15:34:34Z

Also ran into this problem in my gitlab pipeline. Cause is definitely the self update.

Resolved by running rustup set auto-self-update disable before my other commands.

djc · 2024-06-24T15:46:15Z

Reminds me we should probably disable self updates when CI is set in the environment.

Xenira · 2024-06-24T16:20:03Z

Relevant issue: #3824

king-11 · 2024-10-22T17:56:42Z

@Xenira thanks for the resolution.

remove rustfmt download step cargo fmt Changelog-None: ci changes for cache handling disable rustup auto update as it fails: rust-lang/rustup#2886 (comment) Signed-off-by: Lakshya Singh <[email protected]>

hoodmane · 2025-01-16T12:32:00Z

If I understand correctly, there hasn't been a release since rustup 1.27.1 (54dd3d0 2024-04-24), 9 months ago. In particular, this problem still exists in the latest stable rustup? Can we reopen this issue until there is a rustup release? Generally if I see an issue has been closed for 7 months, I figure that it is resolved in the latest stable release.

rami3l · 2025-01-16T13:00:27Z

If I understand correctly, there hasn't been a release since rustup 1.27.1 (54dd3d0 2024-04-24), 9 months ago. In particular, this problem still exists in the latest stable rustup? Can we reopen this issue until there is a rustup release? Generally if I see an issue has been closed for 7 months, I figure that it is resolved in the latest stable release.

@hoodmane I understand your confusion. Unfortunately, GitHub's auto-closing feature is linked to PRs, so keeping resolved issues open makes it difficult to track which ones are already addressed on our side. Currently the best way to find out is probably looking at the "milestone" field to know which fixes belong to which releases... Sorry again for my not adding the milestone for this particular issue previously.

hoodmane · 2025-01-16T13:03:52Z

If rustup doesn't have any timeline for releasing 1.28, could you backport this fix and release a 1.27.2?

djc · 2025-01-16T13:30:53Z

I think it's pretty common practice in both open source and proprietary projects to close an issue once resolved on the development branch.

hoodmane · 2025-01-16T13:39:56Z

Indeed, apologies for the whining. And thanks for contributing the fix!

bbros-dev added the bug label Oct 30, 2021

rbtcollins added the inactive label Dec 11, 2021

bbros-dev changed the title ~~error: rustup is not installed at '/home/hedge/.cargo'~~ error: rustup is not installed at '/home/user/.cargo' Jan 26, 2022

bbros-dev changed the title ~~error: rustup is not installed at '/home/user/.cargo'~~ error: rustup is not installed at '/home/user/.cargo' when $RUSTUP_HOME is set to something other than the former Mar 9, 2022

bbros-dev mentioned this issue Mar 10, 2022

rustup show: Can, instead, configure your system (silently) #2957

Closed

djc mentioned this issue Jun 25, 2024

Disable automatic self updates in CI environments #3907

Merged

djc closed this as completed in #3907 Jun 25, 2024

hoodmane mentioned this issue Jan 16, 2025

rustup is not installed at '/root/.cargo pyodide/pyodide#5345

Closed

rami3l added this to the 1.28.0 milestone Jan 16, 2025

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

error: rustup is not installed at '/home/user/.cargo' when $RUSTUP_HOME is set to something other than the former #2886

error: rustup is not installed at '/home/user/.cargo' when $RUSTUP_HOME is set to something other than the former #2886

bbros-dev commented Oct 30, 2021 •

edited

Loading

kinnison commented Nov 8, 2021

rbtcollins commented Dec 11, 2021

kennystrawnmusic commented Dec 28, 2021 •

edited

Loading

bbros-dev commented Jan 26, 2022

kennystrawnmusic commented Jan 27, 2022 •

edited

Loading

krishnachittur commented Feb 4, 2022

bbros-dev commented Mar 10, 2022

krishnachittur commented Mar 10, 2022

danieleades commented Feb 28, 2024

kinnison commented Feb 29, 2024

danieleades commented Feb 29, 2024

Xenira commented Jun 24, 2024

djc commented Jun 24, 2024

Xenira commented Jun 24, 2024

king-11 commented Oct 22, 2024

hoodmane commented Jan 16, 2025

rami3l commented Jan 16, 2025

hoodmane commented Jan 16, 2025

djc commented Jan 16, 2025

hoodmane commented Jan 16, 2025

error: rustup is not installed at '/home/user/.cargo' when $RUSTUP_HOME is set to something other than the former #2886

error: rustup is not installed at '/home/user/.cargo' when $RUSTUP_HOME is set to something other than the former #2886

Comments

bbros-dev commented Oct 30, 2021 • edited Loading

kinnison commented Nov 8, 2021

rbtcollins commented Dec 11, 2021

kennystrawnmusic commented Dec 28, 2021 • edited Loading

bbros-dev commented Jan 26, 2022

kennystrawnmusic commented Jan 27, 2022 • edited Loading

krishnachittur commented Feb 4, 2022

bbros-dev commented Mar 10, 2022

krishnachittur commented Mar 10, 2022

danieleades commented Feb 28, 2024

kinnison commented Feb 29, 2024

danieleades commented Feb 29, 2024

Xenira commented Jun 24, 2024

djc commented Jun 24, 2024

Xenira commented Jun 24, 2024

king-11 commented Oct 22, 2024

hoodmane commented Jan 16, 2025

rami3l commented Jan 16, 2025

hoodmane commented Jan 16, 2025

djc commented Jan 16, 2025

hoodmane commented Jan 16, 2025

bbros-dev commented Oct 30, 2021 •

edited

Loading

kennystrawnmusic commented Dec 28, 2021 •

edited

Loading

kennystrawnmusic commented Jan 27, 2022 •

edited

Loading