sudo apt install apt-transport-https ca-certificates curl software-properties-common<\/pre>2. Add Docker’s Official GPG Key<\/h3>
To ensure the authenticity and security of the Docker packages, you need to add Docker’s official GPG key and set up the Docker repository. Here’s the guide:<\/p>
\n- Run the following curl command<\/a> to add Docker’s GPG key:<\/li>\n<\/ol>
curl -fsSL https:\/\/download.docker.com\/linux\/ubuntu\/gpg | sudo gpg --dearmor -o \/usr\/share\/keyrings\/docker-archive-keyring.gpg<\/pre>\n- Add the official Docker repository to your APT sources:<\/li>\n<\/ol>
echo \"deb [arch=amd64 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<\/pre>\n- Update your package list to include packages from the new repository:<\/li>\n<\/ol>
sudo apt update<\/pre>3. Install Docker<\/h3>
With the necessary repositories set up, you can now proceed to install Docker. Here are the steps to do so:<\/p>
\n- Make sure you’re about to install Docker from its official repository instead of the default Ubuntu repository:<\/li>\n<\/ol>
apt-cache policy docker-ce<\/pre>\n- You’ll see the following output, indicating that Docker will be installed from the correct repository:<\/li>\n<\/ol>
docker-ce:
Installed: (none)
Candidate: 5:26.1.3-1~ubuntu.24.04~noble
Version table:
5:26.1.3-1~ubuntu.24.04~noble 500
500 https:\/\/download.docker.com\/linux\/ubuntu noble\/stable amd64 Packages
5:26.1.2-1~ubuntu.24.04~noble 500
500 https:\/\/download.docker.com\/linux\/ubuntu noble\/stable amd64 Packages
5:26.1.1-1~ubuntu.24.04~noble 500
500 https:\/\/download.docker.com\/linux\/ubuntu noble\/stable amd64 Packages
…<\/pre>\n- Execute this command to install Docker Engine, Docker Community Edition, and containerd<\/strong> runtime, all necessary for running Docker containers:<\/li>\n<\/ol>
sudo apt install docker-ce docker-ce-cli containerd.io<\/pre>\n- Ensure Docker starts automatically when your system boots:<\/li>\n<\/ol>
sudo systemctl enable docker<\/pre>4. Verify Docker Installation<\/h3>
After installing Docker, it’s important to verify that the installation was successful and that Docker is running correctly. Here are the instructions:<\/p>
\n- Confirm the Docker version installed on your system:<\/li>\n<\/ol>
docker --version<\/pre>\n- Here’s the expected output:<\/li>\n<\/ol>
Docker version 26.1.3, build b72abbb<\/pre>\n- Use the following command to check the Docker service’s status:<\/li>\n<\/ol>
sudo systemctl status docker<\/pre>\n- You should see an output indicating that Docker is active and running:<\/li>\n<\/ol>
● docker.service - Docker Application Container Engine
Loaded: loaded (\/usr\/lib\/systemd\/system\/docker.service; enabled; preset: enabled)
Active: active (running) since Wed 2024-05-22 06:12:32 UTC; 39s ago
TriggeredBy: ● docker.socket
Docs: https:\/\/docs.docker.com
Main PID: 3717 (dockerd)
Tasks: 9
Memory: 29.4M (peak: 29.8M)
CPU: 334ms
CGroup: \/system.slice\/docker.service
└─3717 \/usr\/bin\/dockerd -H fd:\/\/ --containerd=\/run\/containerd\/containerd.sock<\/pre>\n- To exit from this status screen, press Ctrl + C<\/strong> on your keyboard.<\/li>\n<\/ol>
5. Run Docker Without Sudo (Optional)<\/h3>
By default, Docker only allows you to run its commands as a root user with sudo<\/strong> privileges, which can be inconvenient and potentially less secure. If you attempt to run Docker commands as a non-root user, you might see an error like this:<\/p>docker: Cannot connect to the Docker daemon at unix:\/\/\/var\/run\/docker.sock. Is the docker daemon running?.<\/pre>However, running Docker without sudo<\/strong> is more advisable because it’s quicker and simpler. Follow this guide:<\/p>\n- Run the following command to create the docker<\/strong> group:<\/li>\n<\/ol>
sudo groupadd docker<\/pre>\n- Add a new user if you don’t have one. Here, we name it new_user<\/strong>:<\/li>\n<\/ol>
sudo usermod -aG docker new_user<\/pre>\n- You’ll be prompted to set up a new password for this user.<\/li>\n\n\n\n
- Add new_user<\/strong> to the docker<\/strong> group:<\/li>\n<\/ol>
sudo usermod -aG docker new_user<\/pre>\n- Switch to the recently created user:<\/li>\n<\/ol>
su - new_user<\/pre>\n- Verify that this user is part of the docker<\/strong> group:<\/li>\n<\/ol>
groups<\/pre>\n- Here’s the output:<\/li>\n<\/ol>
new_user users docker<\/pre>\n- Run a simple Docker command to verify that you can run commands without sudo<\/strong>:<\/li>\n<\/ol>
docker run hello-world<\/pre>\n- You should see an output showing that Docker is running correctly as a non-root user:<\/li>\n<\/ol>
Unable to find image 'hello-world:latest' locally
latest: Pulling from library\/hello-world
c1ec31eb5944: Pull complete
Digest: sha256:266b191e926f65542fa8daaec01a192c4d292bff79426f47300a046e1bc576fd
Status: Downloaded newer image for hello-world:latest
Hello from Docker!
This message shows that your installation appears to be working correctly.<\/pre>Congratulations! You’ve successfully set up Docker manually on an Ubuntu VPS using commands.<\/p>
Troubleshooting Common Docker Installation Issues<\/h2>
Installing Docker can sometimes come with challenges. Here are some common issues and actionable tips to resolve them.<\/p>
Docker Daemon Not Running<\/strong><\/p>If you receive an error message indicating that the Docker daemon is not running, it likely means the service is not active. To resolve this, start the Docker service using the command:<\/p>
sudo systemctl start docker<\/pre>You can verify the Docker daemon’s status by running:<\/p>
sudo systemctl status docker<\/pre>Cannot Connect to the Docker Daemon<\/strong><\/p>If you encounter the “Cannot connect to the Docker daemon at unix:\/\/\/var\/run\/docker.sock” error, it usually means the Docker service is not running or there are permission issues.<\/p>
First, make sure the Docker service is running with:<\/p>
sudo systemctl start docker<\/pre>Then, verify that your user is part of the Docker group by running the following:<\/p>
groups<\/pre>To solve permission denied issues<\/a>, follow our detailed tutorial.<\/p>Installation Issues from Repositories<\/strong><\/p>Problems when adding the Docker APT repository or during package installation can arise from incorrect repository setup. Make sure you have added the official repository and updated your package list by running:<\/p>
sudo add-apt-repository \"deb [arch=amd64] https:\/\/download.docker.com\/linux\/ubuntu $(lsb_release -cs) stable\"
sudo apt update<\/pre>Running Containers Not Responding<\/strong><\/p>If running containers are not responding or behaving unexpectedly, check the container logs to diagnose the issue. Use the command:<\/p>
docker logs container_id<\/pre>Alternatively, Hostinger VPS users can use the Kodee<\/strong> AI Assistant to check their container logs. Simply ask, “Can you check the logs of the [container_name] container?” like the following example:<\/p>
![\"The](\"https:\/\/www.hostinger.com\/tutorials\/wp-content\/uploads\/sites\/2\/2019\/03\/os-panel-menu-sidebar-hpanel.png\")