How to Fix ‘apt-get command not found’ Error

By
Edwin
aptget

apt_get commandHave you encountered the frustrating “apt-get command not found” error? This article will help you understand why this error occurs and how to fix it across different scenarios.

What are Some of Causes of This Error?

The “apt-get command not found” error typically occurs due to:

  • Non-Debian based Linux distribution
  • Corrupted PATH variable
  • Incomplete system installation
  • Broken package management system
  • Missing symbolic links

How Do You Fix This

To troubleshoot this error you need to follow the following steps;

1. Verify Linux Distribution

First, check if you’re using a Debian-based distribution:

Check operating system cat /etc/os-release
Alternative method lsb_release -a
Check distribution family cat /etc/*-release

2. Fix PATH Environment Variable

Check current PATH

echo $PATH

# Add apt-get to PATH if missing
export PATH=$PATH:/usr/bin:/bin:/usr/sbin:/sbin

Make it permanent
echo 'export PATH=$PATH:/usr/bin:/bin:/usr/sbin:/sbin' >> ~/.bashrc
source ~/.bashrc

3. Install apt-get

For Debian/Ubuntu systems

Update package lists using direct path /usr/bin/apt-get update
Install apt if missing /usr/bin/apt-get install apt

Distribution-Specific Solutions

For Non-Debian Systems

RHEL/CentOS/Fedora (Using dnf/yum):

Install packages
sudo dnf install package_name 
sudo yum install package_name

Arch Linux (Using pacman):

Install packages
sudo pacman -S package_name

OpenSUSE (Using zypper):

Install packages
sudo zypper install package_name

Advanced Troubleshooting

1. Repair Package Management System

Reconfigure dpkg
sudo dpkg --configure -a
Fix broken packages
sudo /usr/bin/apt --fix-broken install
Clean package cache
sudo /usr/bin/apt-get clean
sudo /usr/bin/apt-get autoclean

2. Restore Symbolic Links

Check symbolic links
ls -l /usr/bin/apt-get
Create symbolic link if missing
sudo ln -s /usr/bin/apt-get /usr/bin/apt-get
Verify link creation
which apt-get

3. Check File Permissions

Check permissions ls -l /usr/bin/apt-get
Fix permissions if needed sudo chmod 755 /usr/bin/apt-get
Fix ownership sudo chown root:root /usr/bin/apt-get

Alternative Package Managers

If apt-get isn’t available, you can consider these alternatives:

1. Using apt (Modern Alternative)

Update packages
sudo apt update
Install software
sudo apt install package_name

2. Using dpkg (Low-level Alternative)

Install package
sudo dpkg -i package.deb
Remove package
sudo dpkg -r package_name

Preventive Measures

  1. Regular System Updates
Using apt
sudo apt update && sudo apt upgrade
Using apt-get (when available)
sudo apt-get update && sudo apt-get upgrade
  1. Backup Important Configurations
Backup sources.list
sudo cp /etc/apt/sources.list /etc/apt/sources.list.backup
Backup complete apt directory
sudo cp -r /etc/apt /etc/apt.backup

Common Scenarios and Solutions

1. After System Update

Refresh system
sudo sync
sudo ldconfig
Update shell source ~/.bashrc

2. In Docker Containers

In Dockerfile RUN
apt-get update || apt update

3. In Minimal Installations

Install essential packages
sudo /usr/bin/apt-get install apt-utils apt-transport-https

Troubleshooting Tools

1. System Information

Check system architecture uname -a

Check available disk space df -h

# Check memory usage
free -h

2. Package Management Diagnostics

Check dpkg status dpkg --audit
Verify package database sudo apt-get check
By following this guide you are guaranteed to fix the apt-get command not found’ Error in no time.
More Articles from Unixmen