Fixing “sudo: command not found” on Linux

Seeing "sudo: command not found" errors doesn't always mean you need to install the sudo program. There may be other reasons for the issue. Begin by determining your account identity and how your shell locates the sudo command. Issue commands such as whoami, id -u, ls -l /usr/bin/sudo, and echo $PATH followed by type sudo. If id -u outputs 0, you are operating as the root user.

If /usr/bin/sudo exists but type sudo cannot locate it, examine the PATH variable. If the binary file is missing, root access is required to install it. The source outlines several potential problems, including the shell not finding sudo, the user not being in the sudoers file, and the sudo command itself being absent. It advises not to reinstall sudo if you are already root, as root privileges already include elevated access.

To install sudo, switch to a root shell or use another authorized method to gain root access, then utilize the appropriate package manager for your distribution. For Debian-based systems, use su - to become root and then run apt update and apt install -y sudo. Then add your user account to the sudo group using usermod -aG sudo yourusername.

For other distributions, refer to similar commands such as pacman -S sudo on Arch, dnf install -y sudo on Fedora, or apk add sudo on Alpine. Sometimes, authorization issues arise even when sudo is installed. In this case, investigate the distribution's specific configuration methods. After confirming the installation, check whether the PATH environment variable or shell startup files are causing any issues.

Commands like echo $PATH and type sudo can help identify problems with the PATH variable or unintended aliases. If necessary, modify the relevant startup files or aliases and restart your shell session. For minimal containers or new server accounts, remember that omitting sudo is often intentional due to resource constraints. When setting up a new user with administrative privileges, treat creating the user, installing sudo, and granting sudo permissions as separate tasks.

To simplify troubleshooting, follow a step-by-step order: check your current user identity, look for the existence of /usr/bin/sudo, validate the PATH variable, and finally, verify sudoers authorization if needed.