How to Update Docker on Ubuntu 16.04

Prerequisites and Preparation

Before initiating any changes to your containerization environment, it is crucial to ensure that no containers are currently running. Stopping active services prevents data corruption and service interruptions during the package transition. You can check for running containers using docker ps. If any are present, stop them gracefully with docker stop <container_id>. Additionally, verify your current Docker version to understand what you are replacing. Run docker --version in your terminal. This output helps confirm whether you are dealing with an outdated installation or a legacy setup that requires specific migration steps.

It is also important to back up any critical configuration files located in /etc/docker/, such as daemon.json. While the update process generally preserves these settings, having a copy ensures you can restore custom networking or storage drivers if something goes wrong. If you have previously modified your shell profile to alias Docker commands, note those changes down as well. For users managing complex environments, consider checking related resources like Fixing E: Sub-process /usr/bin/dpkg returned an error code (1) on Kali Linux to anticipate potential package manager issues.

Removing Old Docker Packages

Ubuntu 16.04 often comes with pre-installed versions of Docker or relies on third-party repositories that may conflict with the official Docker CE release. To avoid dependency hell, you need to remove all existing Docker-related packages. Execute the following command to uninstall the old packages:

sudo apt-get purge docker docker-engine docker.io containerd runc

This command uses purge instead of just remove, which ensures that configuration files associated with the old packages are also deleted. After running this, check if any residual configurations remain by listing installed packages with dpkg -l | grep docker. If any appear, remove them individually. It is also wise to remove the old repository sources from /etc/apt/sources.list.d/ to prevent APT from trying to fetch packages from the wrong location later. Clean up unused dependencies with sudo apt-get autoremove to free up disk space and reduce clutter.

Setting Up the Repository

Once the old software is cleared, you need to configure the new Docker repository. Start by installing the necessary prerequisites that allow APT to use HTTPS sources. Run:

sudo apt-get install apt-transport-https ca-certificates curl gnupg lsb-release

Next, add the official Docker GPG key to your system. This step verifies the integrity of the packages you will download. Use the following command to fetch the key:

curl -fsSL https://download.docker.com/linux/ubuntu/gpg | sudo gpg --dearmor -o /usr/share/keyrings/docker-archive-keyring.gpg

After securing the key, add the Docker repository itself. For Ubuntu 16.04 (codename Xenial), use:

echo "deb [arch=amd64 signed-by=/usr/share/keyrings/docker-archive-keyring.gpg] https://download.docker.com/linux/ubuntu xenial stable" | sudo tee /etc/apt/sources.list.d/docker.list

This line tells your package manager exactly where to find the latest Docker Community Edition packages. The signed-by parameter links the repository to the GPG key you just added, ensuring secure downloads. If you encounter errors here, refer to guides on Troubleshooting Linux RHEL 7 for general Linux package management troubleshooting techniques that might apply to similar repository configuration issues.

Installing and Verifying Docker

With the repository configured, update your local package index to include the new Docker packages. Run sudo apt-get update. This step is critical because it refreshes the list of available software from all configured sources, including the newly added Docker repo. Once updated, install the latest version of Docker Engine:

sudo apt-get install docker-ce docker-ce-cli containerd.io

This command installs the core engine, the command-line interface, and the container runtime. Unlike previous versions, Docker CE separates these components for better modularity. After installation completes, verify that the service is active by checking its status with sudo systemctl status docker. You should see an "active (running)" message. Finally, test the installation by running a simple hello-world container:

sudo docker run hello-world

If the container runs successfully and prints a welcome message, your update is complete. Ensure that your user has permission to run Docker commands without sudo by adding your user to the docker group, as detailed in standard Docker documentation. Regularly updating your Docker installation is essential for security and performance, much like how How to Improve Bash Performance and Secure Passwords emphasizes maintaining secure and efficient system environments.

Frequently Asked Questions

Will updating Docker delete my existing containers?

No, updating the Docker packages does not automatically delete your containers or images. However, it is best practice to stop all running containers before performing the upgrade to ensure data consistency. Your volumes and network configurations remain intact unless you explicitly purge the old packages incorrectly.

Why did my Docker service fail to start after the update?

This usually happens due to conflicting configuration files from the old installation or missing dependencies. Check the journal logs using journalctl -u docker.service for specific error messages. Often, removing residual config files in /etc/docker/ and restarting the daemon resolves the issue.

Can I pin Docker to a specific version?

Yes, you can install a specific version by appending the version string to the package name, such as docker-ce=5:19.03.9~3-0~ubuntu-xenial. First, list available versions with apt-cache policy docker-ce, then specify the exact version in the install command. This is useful for environments requiring strict stability over new features.

What should I do if apt-get update fails?

A failed update often indicates a problem with the repository URL or GPG key. Verify that your internet connection is stable and that the repository line in /etc/apt/sources.list.d/docker.list matches your Ubuntu codename. Clearing the APT cache with sudo apt-get clean and retrying can also help resolve temporary glitches.

Is it safe to run Docker as root after updating?

While Docker can run as root, it is recommended to create a non-root user and add them to the docker group. Running Docker as root poses security risks if the daemon is compromised. After updating, ensure your user permissions are correctly set by adding your username to the docker group with sudo usermod -aG docker $USER.