Immediate Fix: Reset GPG Keys and Repository
Most “apt-get update docker-ce failed” errors occur due to expired GPG keys or outdated repository URLs. The fastest way to fix this is to purge the existing Docker repository configuration and re-add the official Docker sources.
| Error Symptom | Primary Cause | Resolution |
|---|---|---|
| GPG error: Key is expired | Outdated Docker GPG Key | Update GPG Key from Docker servers |
| 404 Not Found | Wrong OS Codename | Check /etc/os-release |
| Certificate verification failed | System clock or CA certs | Update ca-certificates |
Run the following command block to refresh your repository settings and fix the signature issues:
# Remove old GPG keys
sudo rm /usr/share/keyrings/docker-archive-keyring.gpg
# Download the latest GPG key
curl -fsSL https://download.docker.com/linux/ubuntu/gpg | sudo gpg --dearmor -o /usr/share/keyrings/docker-archive-keyring.gpg
# Re-add the repository
echo "deb [arch=$(dpkg --print-architecture) signed-by=/usr/share/keyrings/docker-archive-keyring.gpg] https://download.docker.com/linux/ubuntu $(lsb_release -cs) stable" | sudo tee /etc/apt/sources.list.d/docker.list > /dev/null
# Update and install
sudo apt-get update && sudo apt-get install docker-ce docker-ce-cli containerd.ioTechnical Explanation
The “apt-get update” command fails when the APT package manager cannot verify the integrity of the Docker repository. This is usually a security measure to prevent the installation of compromised software.
GPG Key Mismatches
Docker periodically rotates their signing keys. If your system holds an old key, APT will reject the metadata from Docker’s servers, resulting in a “Signature Verification Failed” error.
Repository URL Changes
If you recently upgraded your Linux distribution (e.g., from Ubuntu 20.04 to 22.04), your source list might still point to the old distribution codename. Since Docker maintains specific builds for each version, the old URL will return a 404 error.
Alternative Methods
If the manual GPG update does not resolve the issue, you can try using the official Docker convenience script. This script automates the detection of your operating system and configures the repository for you.
curl -fsSL https://get.docker.com -o get-docker.sh
sudo sh get-docker.shChecking for Conflicting Packages
Sometimes, pre-installed versions of Docker (like docker.io or podman) conflict with the official docker-ce package. Removing these can clear up dependency pathing issues.
for pkg in docker.io docker-doc docker-compose podman-docker containerd runc; do sudo apt-get remove $pkg; doneManual Package Installation
In restrictive network environments where `apt-get` is blocked, you can manually download the `.deb` files from the Docker Download Portal and install them using dpkg -i.