Fix: bash: command not found

The Error

You type a command in the terminal and get:

bash: docker: command not found

Or variations:

zsh: command not found: node

-bash: terraform: command not found

sh: kubectl: not found

The shell cannot find the program you are trying to run. The command either is not installed, or is installed but not in a directory listed in your PATH environment variable.

Why This Happens

When you type a command like docker, the shell searches through directories listed in the PATH variable for an executable file named docker. If it does not find one, it reports command not found.

Common causes:

• The program is not installed. You need to install it first.
• The program is installed but not in PATH. The binary is somewhere on the system, but the directory is not in PATH.
• You just installed it but the shell is not refreshed. The shell cached the old PATH. A new terminal or source ~/.bashrc is needed.
• Wrong shell. You configured PATH in ~/.bashrc but you are using zsh (which reads ~/.zshrc).
• Typo. You misspelled the command name.
• Broken symbolic link. A symlink in /usr/local/bin points to a deleted file.
• Sudo environment. Running with sudo uses a different PATH.

Fix 1: Install the Program

The program might simply not be installed. Install it with your system’s package manager:

Ubuntu/Debian:

sudo apt update
sudo apt install <package-name>

Fedora/RHEL/CentOS:

sudo dnf install <package-name>

macOS (Homebrew):

brew install <package-name>

Arch Linux:

sudo pacman -S <package-name>

Common packages and their install commands:

If apt cannot find the package, see Fix: apt-get unable to locate package.

Fix 2: Add the Binary to PATH

The program is installed but its directory is not in PATH:

Find where the program is:

find / -name "docker" -type f 2>/dev/null
which docker
whereis docker

Common directories not in PATH by default:

• ~/.local/bin — pip-installed Python tools
• /usr/local/go/bin — Go installation
• ~/go/bin — Go workspace binaries
• ~/.cargo/bin — Rust/cargo binaries
• ~/.nvm/versions/node/v20.x/bin — NVM-managed Node.js
• /snap/bin — Snap packages
• /opt/<program>/bin — Optional software

Add a directory to PATH:

export PATH="$PATH:/path/to/directory"

Make it permanent. Add the export line to your shell configuration file:

For bash (~/.bashrc or ~/.bash_profile):

echo 'export PATH="$PATH:$HOME/.local/bin"' >> ~/.bashrc
source ~/.bashrc

For zsh (~/.zshrc):

echo 'export PATH="$PATH:$HOME/.local/bin"' >> ~/.zshrc
source ~/.zshrc

Pro Tip: Check which shell you are using with echo $SHELL. If it says /bin/zsh, edit ~/.zshrc. If it says /bin/bash, edit ~/.bashrc. Editing the wrong file is the #1 reason PATH changes “don’t work.”

Fix 3: Refresh Your Shell Session

After installing a program or modifying PATH, the current shell might have a cached lookup table:

# Reload shell config
source ~/.bashrc    # for bash
source ~/.zshrc     # for zsh

# Or clear the command hash table
hash -r

Or simply open a new terminal window. New terminals always read the latest configuration.

SSH sessions: If you installed something and then SSH’d in, the SSH session might have a cached PATH. Disconnect and reconnect.

Fix 4: Fix sudo PATH Issues

Commands that work without sudo might fail with sudo:

node --version    # Works
sudo node --version  # command not found

sudo uses a restricted PATH (defined by secure_path in /etc/sudoers). Your user PATH additions are not available.

Fix: Use the full path:

sudo /home/user/.nvm/versions/node/v20.12.0/bin/node --version

Fix: Preserve PATH with sudo:

sudo env "PATH=$PATH" node --version

Fix: Edit sudoers to include the path (permanent):

sudo visudo

Find the secure_path line and add your directory:

Defaults secure_path="/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/snap/bin"

Fix 5: Fix Version Manager Commands

Version managers (nvm, pyenv, rbenv, sdkman) install binaries in custom directories and require initialization:

Node.js (nvm):

# Add to ~/.bashrc or ~/.zshrc:
export NVM_DIR="$HOME/.nvm"
[ -s "$NVM_DIR/nvm.sh" ] && \. "$NVM_DIR/nvm.sh"

Then:

source ~/.bashrc
nvm install 20
node --version

Python (pyenv):

# Add to ~/.bashrc or ~/.zshrc:
export PYENV_ROOT="$HOME/.pyenv"
export PATH="$PYENV_ROOT/bin:$PATH"
eval "$(pyenv init -)"

For Python-specific command not found issues, see Fix: python command not found.

Ruby (rbenv):

eval "$(rbenv init -)"

Common Mistake: Installing a version manager but forgetting to add its initialization to your shell config. The manager installs successfully, but its commands are not available in new terminal sessions. Always follow the post-install instructions.

Fix 6: Fix Broken Symbolic Links

A broken symlink in /usr/local/bin or /usr/bin can cause command not found even though ls shows the file:

ls -la /usr/local/bin/terraform
# lrwxrwxrwx 1 root root 35 Jan 1 /usr/local/bin/terraform -> /opt/terraform/0.14/terraform
# The target might not exist anymore

Check if the link is broken:

file /usr/local/bin/terraform
# /usr/local/bin/terraform: broken symbolic link to /opt/terraform/0.14/terraform

Fix: Remove the broken link and recreate it:

sudo rm /usr/local/bin/terraform
sudo ln -s /opt/terraform/1.7/terraform /usr/local/bin/terraform

Or reinstall the program to recreate the link automatically.

Fix 7: Fix Commands Inside Scripts

If a command works in your terminal but fails in a script:

#!/bin/bash
docker compose up  # command not found

The script uses a different PATH. Add the PATH at the top of the script:

#!/bin/bash
export PATH="/usr/local/bin:$PATH"
docker compose up

Or use the full path:

#!/bin/bash
/usr/local/bin/docker compose up

Check the shebang line. #!/bin/sh uses a minimal POSIX shell, not bash. Some features and PATH settings might differ:

#!/bin/bash    # Use bash
#!/usr/bin/env bash  # More portable — finds bash in PATH

If the script has permission issues, see Fix: bash permission denied.

Fix 8: Fix Docker Container Commands

Inside Docker containers, commands available on the host are not automatically available:

docker exec -it mycontainer bash
# Inside container:
curl http://example.com
# bash: curl: command not found

Fix: Install the tool in the Dockerfile:

FROM ubuntu:24.04
RUN apt-get update && apt-get install -y curl wget vim

Or for Alpine-based images:

FROM alpine:3.19
RUN apk add --no-cache curl wget

For Docker-specific issues, see Fix: Docker daemon is not running.

Still Not Working?

If the command is still not found:

Check for typos:

dcoker --version    # Typo: "dcoker" instead of "docker"
pytohn --version    # Typo: "pytohn" instead of "python"

Check for aliases. Some commands are aliases defined in your shell config:

alias | grep <command>
type <command>

If the command is an alias and you’re in a script, aliases might not be loaded. Use the full command name.

Check if the command is a shell builtin:

type cd      # cd is a shell builtin
type echo    # echo is a shell builtin

Builtins are part of the shell, not external programs. They are always available.

Check for architecture mismatch. On Apple Silicon Macs (M1/M2/M3), x86 binaries need Rosetta. On ARM Linux, x86 binaries do not run natively. Check the binary architecture:

file $(which <command>)

Check snap and flatpak. If the program was installed via snap or flatpak, it might be in a different location:

snap list
flatpak list

For SSH connection issues that prevent you from reaching the server where the command is installed, see Fix: SSH connection timed out.