Variable path issue : conda command not found
After installing Anaconda correctly. l wanted after finishing the installation to do the following. l forget to do it while installing anaconda:
export PATH="/root/anaconda3/bin"
conda --version
conda command not found
then l opened
gedit /root/.bashrc
l added at the end of file
export PATH="/root/anaconda3/bin"
butt l still get
conda --version
conda command not found
EDIT1: gedit /root/.bashrc
# ~/.bashrc: executed by bash(1) for non-login shells.
# see /usr/share/doc/bash/examples/startup-files (in the package bash-doc)
# for examples
# If not running interactively, don't do anything
[ -z "$PS1" ] && return
# don't put duplicate lines in the history. See bash(1) for more options
# ... or force ignoredups and ignorespace
HISTCONTROL=ignoredups:ignorespace
# append to the history file, don't overwrite it
shopt -s histappend
# for setting history length see HISTSIZE and HISTFILESIZE in bash(1)
HISTSIZE=1000
HISTFILESIZE=2000
# check the window size after each command and, if necessary,
# update the values of LINES and COLUMNS.
shopt -s checkwinsize
# make less more friendly for non-text input files, see lesspipe(1)
[ -x /usr/bin/lesspipe ] && eval "$(SHELL=/bin/sh lesspipe)"
# set variable identifying the chroot you work in (used in the prompt below)
if [ -z "$debian_chroot" ] && [ -r /etc/debian_chroot ]; then
debian_chroot=$(cat /etc/debian_chroot)
fi
# set a fancy prompt (non-color, unless we know we "want" color)
case "$TERM" in
xterm-color) color_prompt=yes;;
esac
# uncomment for a colored prompt, if the terminal has the capability; turned
# off by default to not distract the user: the focus in a terminal window
# should be on the output of commands, not on the prompt
#force_color_prompt=yes
if [ -n "$force_color_prompt" ]; then
if [ -x /usr/bin/tput ] && tput setaf 1 >&/dev/null; then
# We have color support; assume it's compliant with Ecma-48
# (ISO/IEC-6429). (Lack of such support is extremely rare, and such
# a case would tend to support setf rather than setaf.)
color_prompt=yes
else
color_prompt=
fi
fi
if [ "$color_prompt" = yes ]; then
PS1='${debian_chroot:+($debian_chroot)}[33[01;32m]u@h[33[00m]:[33[01;34m]w[33[00m]$ '
else
PS1='${debian_chroot:+($debian_chroot)}u@h:w$ '
fi
unset color_prompt force_color_prompt
# If this is an xterm set the title to user@host:dir
case "$TERM" in
xterm*|rxvt*)
PS1="[e]0;${debian_chroot:+($debian_chroot)}u@h: wa]$PS1"
;;
*)
;;
esac
# enable color support of ls and also add handy aliases
if [ -x /usr/bin/dircolors ]; then
test -r ~/.dircolors && eval "$(dircolors -b ~/.dircolors)" || eval "$(dircolors -b)"
alias ls='ls --color=auto'
#alias dir='dir --color=auto'
#alias vdir='vdir --color=auto'
alias grep='grep --color=auto'
alias fgrep='fgrep --color=auto'
alias egrep='egrep --color=auto'
fi
# some more ls aliases
alias ll='ls -alF'
alias la='ls -A'
alias l='ls -CF'
# Alias definitions.
# You may want to put all your additions into a separate file like
# ~/.bash_aliases, instead of adding them here directly.
# See /usr/share/doc/bash-doc/examples in the bash-doc package.
if [ -f ~/.bash_aliases ]; then
. ~/.bash_aliases
fi
# enable programmable completion features (you don't need to enable
# this, if it's already enabled in /etc/bash.bashrc and /etc/profile
# sources /etc/bash.bashrc).
#if [ -f /etc/bash_completion ] && ! shopt -oq posix; then
# . /etc/bash_completion
#fi
l did also the following :
echo $PATH
/home/ahmed/anaconda3/bin:/home/ahmed/anaconda3/bin:/home/ahmed/anaconda3/bin:/home/ahmed/anaconda3/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games
What's wrong with my code ? there are lots path in this path !!
bash paths anaconda conda
add a comment |
After installing Anaconda correctly. l wanted after finishing the installation to do the following. l forget to do it while installing anaconda:
export PATH="/root/anaconda3/bin"
conda --version
conda command not found
then l opened
gedit /root/.bashrc
l added at the end of file
export PATH="/root/anaconda3/bin"
butt l still get
conda --version
conda command not found
EDIT1: gedit /root/.bashrc
# ~/.bashrc: executed by bash(1) for non-login shells.
# see /usr/share/doc/bash/examples/startup-files (in the package bash-doc)
# for examples
# If not running interactively, don't do anything
[ -z "$PS1" ] && return
# don't put duplicate lines in the history. See bash(1) for more options
# ... or force ignoredups and ignorespace
HISTCONTROL=ignoredups:ignorespace
# append to the history file, don't overwrite it
shopt -s histappend
# for setting history length see HISTSIZE and HISTFILESIZE in bash(1)
HISTSIZE=1000
HISTFILESIZE=2000
# check the window size after each command and, if necessary,
# update the values of LINES and COLUMNS.
shopt -s checkwinsize
# make less more friendly for non-text input files, see lesspipe(1)
[ -x /usr/bin/lesspipe ] && eval "$(SHELL=/bin/sh lesspipe)"
# set variable identifying the chroot you work in (used in the prompt below)
if [ -z "$debian_chroot" ] && [ -r /etc/debian_chroot ]; then
debian_chroot=$(cat /etc/debian_chroot)
fi
# set a fancy prompt (non-color, unless we know we "want" color)
case "$TERM" in
xterm-color) color_prompt=yes;;
esac
# uncomment for a colored prompt, if the terminal has the capability; turned
# off by default to not distract the user: the focus in a terminal window
# should be on the output of commands, not on the prompt
#force_color_prompt=yes
if [ -n "$force_color_prompt" ]; then
if [ -x /usr/bin/tput ] && tput setaf 1 >&/dev/null; then
# We have color support; assume it's compliant with Ecma-48
# (ISO/IEC-6429). (Lack of such support is extremely rare, and such
# a case would tend to support setf rather than setaf.)
color_prompt=yes
else
color_prompt=
fi
fi
if [ "$color_prompt" = yes ]; then
PS1='${debian_chroot:+($debian_chroot)}[33[01;32m]u@h[33[00m]:[33[01;34m]w[33[00m]$ '
else
PS1='${debian_chroot:+($debian_chroot)}u@h:w$ '
fi
unset color_prompt force_color_prompt
# If this is an xterm set the title to user@host:dir
case "$TERM" in
xterm*|rxvt*)
PS1="[e]0;${debian_chroot:+($debian_chroot)}u@h: wa]$PS1"
;;
*)
;;
esac
# enable color support of ls and also add handy aliases
if [ -x /usr/bin/dircolors ]; then
test -r ~/.dircolors && eval "$(dircolors -b ~/.dircolors)" || eval "$(dircolors -b)"
alias ls='ls --color=auto'
#alias dir='dir --color=auto'
#alias vdir='vdir --color=auto'
alias grep='grep --color=auto'
alias fgrep='fgrep --color=auto'
alias egrep='egrep --color=auto'
fi
# some more ls aliases
alias ll='ls -alF'
alias la='ls -A'
alias l='ls -CF'
# Alias definitions.
# You may want to put all your additions into a separate file like
# ~/.bash_aliases, instead of adding them here directly.
# See /usr/share/doc/bash-doc/examples in the bash-doc package.
if [ -f ~/.bash_aliases ]; then
. ~/.bash_aliases
fi
# enable programmable completion features (you don't need to enable
# this, if it's already enabled in /etc/bash.bashrc and /etc/profile
# sources /etc/bash.bashrc).
#if [ -f /etc/bash_completion ] && ! shopt -oq posix; then
# . /etc/bash_completion
#fi
l did also the following :
echo $PATH
/home/ahmed/anaconda3/bin:/home/ahmed/anaconda3/bin:/home/ahmed/anaconda3/bin:/home/ahmed/anaconda3/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games
What's wrong with my code ? there are lots path in this path !!
bash paths anaconda conda
Is conda installed in the home folder? What's the output ofll ~/
– M. Becerra
Apr 25 '17 at 16:29
ll ~/ Command 'ls' is available in '/bin/ls' The command could not be located because '/bin' is not included in the PATH environment variable. ls: command not found
– vincent
Apr 25 '17 at 16:29
anaconda3 is installed in /root/anaconda3/
– vincent
Apr 25 '17 at 16:30
You installed it in/root
instead of/home/$USER/
. You must have been in theroot home
when you did so. please move it to/home/$USER
– George Udosen
Apr 25 '17 at 16:33
add a comment |
After installing Anaconda correctly. l wanted after finishing the installation to do the following. l forget to do it while installing anaconda:
export PATH="/root/anaconda3/bin"
conda --version
conda command not found
then l opened
gedit /root/.bashrc
l added at the end of file
export PATH="/root/anaconda3/bin"
butt l still get
conda --version
conda command not found
EDIT1: gedit /root/.bashrc
# ~/.bashrc: executed by bash(1) for non-login shells.
# see /usr/share/doc/bash/examples/startup-files (in the package bash-doc)
# for examples
# If not running interactively, don't do anything
[ -z "$PS1" ] && return
# don't put duplicate lines in the history. See bash(1) for more options
# ... or force ignoredups and ignorespace
HISTCONTROL=ignoredups:ignorespace
# append to the history file, don't overwrite it
shopt -s histappend
# for setting history length see HISTSIZE and HISTFILESIZE in bash(1)
HISTSIZE=1000
HISTFILESIZE=2000
# check the window size after each command and, if necessary,
# update the values of LINES and COLUMNS.
shopt -s checkwinsize
# make less more friendly for non-text input files, see lesspipe(1)
[ -x /usr/bin/lesspipe ] && eval "$(SHELL=/bin/sh lesspipe)"
# set variable identifying the chroot you work in (used in the prompt below)
if [ -z "$debian_chroot" ] && [ -r /etc/debian_chroot ]; then
debian_chroot=$(cat /etc/debian_chroot)
fi
# set a fancy prompt (non-color, unless we know we "want" color)
case "$TERM" in
xterm-color) color_prompt=yes;;
esac
# uncomment for a colored prompt, if the terminal has the capability; turned
# off by default to not distract the user: the focus in a terminal window
# should be on the output of commands, not on the prompt
#force_color_prompt=yes
if [ -n "$force_color_prompt" ]; then
if [ -x /usr/bin/tput ] && tput setaf 1 >&/dev/null; then
# We have color support; assume it's compliant with Ecma-48
# (ISO/IEC-6429). (Lack of such support is extremely rare, and such
# a case would tend to support setf rather than setaf.)
color_prompt=yes
else
color_prompt=
fi
fi
if [ "$color_prompt" = yes ]; then
PS1='${debian_chroot:+($debian_chroot)}[33[01;32m]u@h[33[00m]:[33[01;34m]w[33[00m]$ '
else
PS1='${debian_chroot:+($debian_chroot)}u@h:w$ '
fi
unset color_prompt force_color_prompt
# If this is an xterm set the title to user@host:dir
case "$TERM" in
xterm*|rxvt*)
PS1="[e]0;${debian_chroot:+($debian_chroot)}u@h: wa]$PS1"
;;
*)
;;
esac
# enable color support of ls and also add handy aliases
if [ -x /usr/bin/dircolors ]; then
test -r ~/.dircolors && eval "$(dircolors -b ~/.dircolors)" || eval "$(dircolors -b)"
alias ls='ls --color=auto'
#alias dir='dir --color=auto'
#alias vdir='vdir --color=auto'
alias grep='grep --color=auto'
alias fgrep='fgrep --color=auto'
alias egrep='egrep --color=auto'
fi
# some more ls aliases
alias ll='ls -alF'
alias la='ls -A'
alias l='ls -CF'
# Alias definitions.
# You may want to put all your additions into a separate file like
# ~/.bash_aliases, instead of adding them here directly.
# See /usr/share/doc/bash-doc/examples in the bash-doc package.
if [ -f ~/.bash_aliases ]; then
. ~/.bash_aliases
fi
# enable programmable completion features (you don't need to enable
# this, if it's already enabled in /etc/bash.bashrc and /etc/profile
# sources /etc/bash.bashrc).
#if [ -f /etc/bash_completion ] && ! shopt -oq posix; then
# . /etc/bash_completion
#fi
l did also the following :
echo $PATH
/home/ahmed/anaconda3/bin:/home/ahmed/anaconda3/bin:/home/ahmed/anaconda3/bin:/home/ahmed/anaconda3/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games
What's wrong with my code ? there are lots path in this path !!
bash paths anaconda conda
After installing Anaconda correctly. l wanted after finishing the installation to do the following. l forget to do it while installing anaconda:
export PATH="/root/anaconda3/bin"
conda --version
conda command not found
then l opened
gedit /root/.bashrc
l added at the end of file
export PATH="/root/anaconda3/bin"
butt l still get
conda --version
conda command not found
EDIT1: gedit /root/.bashrc
# ~/.bashrc: executed by bash(1) for non-login shells.
# see /usr/share/doc/bash/examples/startup-files (in the package bash-doc)
# for examples
# If not running interactively, don't do anything
[ -z "$PS1" ] && return
# don't put duplicate lines in the history. See bash(1) for more options
# ... or force ignoredups and ignorespace
HISTCONTROL=ignoredups:ignorespace
# append to the history file, don't overwrite it
shopt -s histappend
# for setting history length see HISTSIZE and HISTFILESIZE in bash(1)
HISTSIZE=1000
HISTFILESIZE=2000
# check the window size after each command and, if necessary,
# update the values of LINES and COLUMNS.
shopt -s checkwinsize
# make less more friendly for non-text input files, see lesspipe(1)
[ -x /usr/bin/lesspipe ] && eval "$(SHELL=/bin/sh lesspipe)"
# set variable identifying the chroot you work in (used in the prompt below)
if [ -z "$debian_chroot" ] && [ -r /etc/debian_chroot ]; then
debian_chroot=$(cat /etc/debian_chroot)
fi
# set a fancy prompt (non-color, unless we know we "want" color)
case "$TERM" in
xterm-color) color_prompt=yes;;
esac
# uncomment for a colored prompt, if the terminal has the capability; turned
# off by default to not distract the user: the focus in a terminal window
# should be on the output of commands, not on the prompt
#force_color_prompt=yes
if [ -n "$force_color_prompt" ]; then
if [ -x /usr/bin/tput ] && tput setaf 1 >&/dev/null; then
# We have color support; assume it's compliant with Ecma-48
# (ISO/IEC-6429). (Lack of such support is extremely rare, and such
# a case would tend to support setf rather than setaf.)
color_prompt=yes
else
color_prompt=
fi
fi
if [ "$color_prompt" = yes ]; then
PS1='${debian_chroot:+($debian_chroot)}[33[01;32m]u@h[33[00m]:[33[01;34m]w[33[00m]$ '
else
PS1='${debian_chroot:+($debian_chroot)}u@h:w$ '
fi
unset color_prompt force_color_prompt
# If this is an xterm set the title to user@host:dir
case "$TERM" in
xterm*|rxvt*)
PS1="[e]0;${debian_chroot:+($debian_chroot)}u@h: wa]$PS1"
;;
*)
;;
esac
# enable color support of ls and also add handy aliases
if [ -x /usr/bin/dircolors ]; then
test -r ~/.dircolors && eval "$(dircolors -b ~/.dircolors)" || eval "$(dircolors -b)"
alias ls='ls --color=auto'
#alias dir='dir --color=auto'
#alias vdir='vdir --color=auto'
alias grep='grep --color=auto'
alias fgrep='fgrep --color=auto'
alias egrep='egrep --color=auto'
fi
# some more ls aliases
alias ll='ls -alF'
alias la='ls -A'
alias l='ls -CF'
# Alias definitions.
# You may want to put all your additions into a separate file like
# ~/.bash_aliases, instead of adding them here directly.
# See /usr/share/doc/bash-doc/examples in the bash-doc package.
if [ -f ~/.bash_aliases ]; then
. ~/.bash_aliases
fi
# enable programmable completion features (you don't need to enable
# this, if it's already enabled in /etc/bash.bashrc and /etc/profile
# sources /etc/bash.bashrc).
#if [ -f /etc/bash_completion ] && ! shopt -oq posix; then
# . /etc/bash_completion
#fi
l did also the following :
echo $PATH
/home/ahmed/anaconda3/bin:/home/ahmed/anaconda3/bin:/home/ahmed/anaconda3/bin:/home/ahmed/anaconda3/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games
What's wrong with my code ? there are lots path in this path !!
bash paths anaconda conda
bash paths anaconda conda
asked Apr 25 '17 at 16:26
vincent vincent
1411311
1411311
Is conda installed in the home folder? What's the output ofll ~/
– M. Becerra
Apr 25 '17 at 16:29
ll ~/ Command 'ls' is available in '/bin/ls' The command could not be located because '/bin' is not included in the PATH environment variable. ls: command not found
– vincent
Apr 25 '17 at 16:29
anaconda3 is installed in /root/anaconda3/
– vincent
Apr 25 '17 at 16:30
You installed it in/root
instead of/home/$USER/
. You must have been in theroot home
when you did so. please move it to/home/$USER
– George Udosen
Apr 25 '17 at 16:33
add a comment |
Is conda installed in the home folder? What's the output ofll ~/
– M. Becerra
Apr 25 '17 at 16:29
ll ~/ Command 'ls' is available in '/bin/ls' The command could not be located because '/bin' is not included in the PATH environment variable. ls: command not found
– vincent
Apr 25 '17 at 16:29
anaconda3 is installed in /root/anaconda3/
– vincent
Apr 25 '17 at 16:30
You installed it in/root
instead of/home/$USER/
. You must have been in theroot home
when you did so. please move it to/home/$USER
– George Udosen
Apr 25 '17 at 16:33
Is conda installed in the home folder? What's the output of
ll ~/
– M. Becerra
Apr 25 '17 at 16:29
Is conda installed in the home folder? What's the output of
ll ~/
– M. Becerra
Apr 25 '17 at 16:29
ll ~/ Command 'ls' is available in '/bin/ls' The command could not be located because '/bin' is not included in the PATH environment variable. ls: command not found
– vincent
Apr 25 '17 at 16:29
ll ~/ Command 'ls' is available in '/bin/ls' The command could not be located because '/bin' is not included in the PATH environment variable. ls: command not found
– vincent
Apr 25 '17 at 16:29
anaconda3 is installed in /root/anaconda3/
– vincent
Apr 25 '17 at 16:30
anaconda3 is installed in /root/anaconda3/
– vincent
Apr 25 '17 at 16:30
You installed it in
/root
instead of /home/$USER/
. You must have been in the root home
when you did so. please move it to /home/$USER
– George Udosen
Apr 25 '17 at 16:33
You installed it in
/root
instead of /home/$USER/
. You must have been in the root home
when you did so. please move it to /home/$USER
– George Udosen
Apr 25 '17 at 16:33
add a comment |
4 Answers
4
active
oldest
votes
Lets fix it like this:
Move it out of
/root/
with:
sudo mv /root/anaconda3 /home/$USER
Add this to
/home/ahmed/.bashrc
please don't use 'sudo' here simple donano /home/$USER/.bashrc
:
# Anaconda3
export PATH="/home/ahmed/anaconda2/bin:$PATH"
Source the
.bashrc
file with:
source /home/ahmed/.bashrc
Now delete the entry [
export PATH="/root/anaconda3/bin"
] in/root/.bashrc
withnano editor
or with the editor you used beforeOpen new terminal and check
add a comment |
Try adding below line to your .bashrc
file
export PATH=~/anaconda3/bin:$PATH
then try:
conda --version
to see version
add a comment |
Make sure that you are installing the Anaconda binary that is compatible with your kernel.
I was in the same situation. Turned out I have an x64_86 CPU and was trying to install a 64 bit Power 8 installer. You can find out the same for your CPU by using the following command. It gives you a basic information about a computer's software and hardware.
$ uname -a
https://www.anaconda.com/download/#linux
The page in the link above, displays 2 different types of 64-Bit installers.
- 64-Bit (x86) installer and
- 64-Bit (Power 8) installer
add a comment |
If you did the installation and PATH configuration, you just need to restart your terminal (in order to consider your changment).
New contributor
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "89"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f908827%2fvariable-path-issue-conda-command-not-found%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
4 Answers
4
active
oldest
votes
4 Answers
4
active
oldest
votes
active
oldest
votes
active
oldest
votes
Lets fix it like this:
Move it out of
/root/
with:
sudo mv /root/anaconda3 /home/$USER
Add this to
/home/ahmed/.bashrc
please don't use 'sudo' here simple donano /home/$USER/.bashrc
:
# Anaconda3
export PATH="/home/ahmed/anaconda2/bin:$PATH"
Source the
.bashrc
file with:
source /home/ahmed/.bashrc
Now delete the entry [
export PATH="/root/anaconda3/bin"
] in/root/.bashrc
withnano editor
or with the editor you used beforeOpen new terminal and check
add a comment |
Lets fix it like this:
Move it out of
/root/
with:
sudo mv /root/anaconda3 /home/$USER
Add this to
/home/ahmed/.bashrc
please don't use 'sudo' here simple donano /home/$USER/.bashrc
:
# Anaconda3
export PATH="/home/ahmed/anaconda2/bin:$PATH"
Source the
.bashrc
file with:
source /home/ahmed/.bashrc
Now delete the entry [
export PATH="/root/anaconda3/bin"
] in/root/.bashrc
withnano editor
or with the editor you used beforeOpen new terminal and check
add a comment |
Lets fix it like this:
Move it out of
/root/
with:
sudo mv /root/anaconda3 /home/$USER
Add this to
/home/ahmed/.bashrc
please don't use 'sudo' here simple donano /home/$USER/.bashrc
:
# Anaconda3
export PATH="/home/ahmed/anaconda2/bin:$PATH"
Source the
.bashrc
file with:
source /home/ahmed/.bashrc
Now delete the entry [
export PATH="/root/anaconda3/bin"
] in/root/.bashrc
withnano editor
or with the editor you used beforeOpen new terminal and check
Lets fix it like this:
Move it out of
/root/
with:
sudo mv /root/anaconda3 /home/$USER
Add this to
/home/ahmed/.bashrc
please don't use 'sudo' here simple donano /home/$USER/.bashrc
:
# Anaconda3
export PATH="/home/ahmed/anaconda2/bin:$PATH"
Source the
.bashrc
file with:
source /home/ahmed/.bashrc
Now delete the entry [
export PATH="/root/anaconda3/bin"
] in/root/.bashrc
withnano editor
or with the editor you used beforeOpen new terminal and check
edited Apr 25 '17 at 17:01
answered Apr 25 '17 at 16:48
George UdosenGeorge Udosen
21.2k94570
21.2k94570
add a comment |
add a comment |
Try adding below line to your .bashrc
file
export PATH=~/anaconda3/bin:$PATH
then try:
conda --version
to see version
add a comment |
Try adding below line to your .bashrc
file
export PATH=~/anaconda3/bin:$PATH
then try:
conda --version
to see version
add a comment |
Try adding below line to your .bashrc
file
export PATH=~/anaconda3/bin:$PATH
then try:
conda --version
to see version
Try adding below line to your .bashrc
file
export PATH=~/anaconda3/bin:$PATH
then try:
conda --version
to see version
edited Aug 5 '18 at 21:42
Stephen Rauch
1,1546716
1,1546716
answered Aug 5 '18 at 15:53
dgamerdgamer
312
312
add a comment |
add a comment |
Make sure that you are installing the Anaconda binary that is compatible with your kernel.
I was in the same situation. Turned out I have an x64_86 CPU and was trying to install a 64 bit Power 8 installer. You can find out the same for your CPU by using the following command. It gives you a basic information about a computer's software and hardware.
$ uname -a
https://www.anaconda.com/download/#linux
The page in the link above, displays 2 different types of 64-Bit installers.
- 64-Bit (x86) installer and
- 64-Bit (Power 8) installer
add a comment |
Make sure that you are installing the Anaconda binary that is compatible with your kernel.
I was in the same situation. Turned out I have an x64_86 CPU and was trying to install a 64 bit Power 8 installer. You can find out the same for your CPU by using the following command. It gives you a basic information about a computer's software and hardware.
$ uname -a
https://www.anaconda.com/download/#linux
The page in the link above, displays 2 different types of 64-Bit installers.
- 64-Bit (x86) installer and
- 64-Bit (Power 8) installer
add a comment |
Make sure that you are installing the Anaconda binary that is compatible with your kernel.
I was in the same situation. Turned out I have an x64_86 CPU and was trying to install a 64 bit Power 8 installer. You can find out the same for your CPU by using the following command. It gives you a basic information about a computer's software and hardware.
$ uname -a
https://www.anaconda.com/download/#linux
The page in the link above, displays 2 different types of 64-Bit installers.
- 64-Bit (x86) installer and
- 64-Bit (Power 8) installer
Make sure that you are installing the Anaconda binary that is compatible with your kernel.
I was in the same situation. Turned out I have an x64_86 CPU and was trying to install a 64 bit Power 8 installer. You can find out the same for your CPU by using the following command. It gives you a basic information about a computer's software and hardware.
$ uname -a
https://www.anaconda.com/download/#linux
The page in the link above, displays 2 different types of 64-Bit installers.
- 64-Bit (x86) installer and
- 64-Bit (Power 8) installer
edited Oct 14 '17 at 13:58
Thomas
3,80981527
3,80981527
answered Oct 14 '17 at 13:21
TaaniTaani
113
113
add a comment |
add a comment |
If you did the installation and PATH configuration, you just need to restart your terminal (in order to consider your changment).
New contributor
add a comment |
If you did the installation and PATH configuration, you just need to restart your terminal (in order to consider your changment).
New contributor
add a comment |
If you did the installation and PATH configuration, you just need to restart your terminal (in order to consider your changment).
New contributor
If you did the installation and PATH configuration, you just need to restart your terminal (in order to consider your changment).
New contributor
New contributor
answered 10 hours ago
Yasmina MekkiYasmina Mekki
1
1
New contributor
New contributor
add a comment |
add a comment |
Thanks for contributing an answer to Ask Ubuntu!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f908827%2fvariable-path-issue-conda-command-not-found%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Is conda installed in the home folder? What's the output of
ll ~/
– M. Becerra
Apr 25 '17 at 16:29
ll ~/ Command 'ls' is available in '/bin/ls' The command could not be located because '/bin' is not included in the PATH environment variable. ls: command not found
– vincent
Apr 25 '17 at 16:29
anaconda3 is installed in /root/anaconda3/
– vincent
Apr 25 '17 at 16:30
You installed it in
/root
instead of/home/$USER/
. You must have been in theroot home
when you did so. please move it to/home/$USER
– George Udosen
Apr 25 '17 at 16:33