Start Docker Daemon on Linux

In This Tutorial, You Will Learn:

• How to manually start the Docker daemon
• How to configure Docker to start automatically at boot time
• How to check the Docker daemon status
• How to troubleshoot common Docker daemon startup issues

Software Requirements and Linux Command Line Conventions

Start Docker Daemon on Linux

The Docker daemon (dockerd) is the persistent process that manages containers on your Linux system. Starting and managing this daemon is essential for working with Docker containers and images. Let’s explore various methods to control the Docker daemon on Linux systems.

How to start, enable and restart docker daemon examples

1. Starting Docker daemon using systemd: Most modern Linux distributions use systemd as their init system.

   $ sudo systemctl start docker

   This command starts the Docker daemon immediately. If the service starts successfully, there will be no output. You can verify the service is running with the status command described in step 3.

2. Enabling Docker to start at boot time: To ensure Docker starts automatically when your system boots.

   $ sudo systemctl enable docker

   This command creates the necessary symbolic links to start Docker during system boot. You should see output indicating that the symlinks were created successfully.

3. Checking Docker daemon status: To verify that the Docker daemon is running properly.

   $ sudo systemctl status docker

   This command shows the current status of the Docker service, including whether it’s active (running), enabled at boot, and recent log entries. Look for “Active: active (running)” to confirm the daemon is running correctly.

4. Starting Docker on older distributions (SysVinit): For Linux distributions using the older SysVinit system.

   $ sudo service docker start

   This command starts the Docker daemon on systems using SysVinit. You can similarly use “docker status” to check if it’s running.

5. Starting Docker daemon manually: In rare cases, you might need to start the daemon directly.

   $ sudo dockerd

   This command starts the Docker daemon in the foreground. Note that this will display all logs to the terminal and the process will stop if you close the terminal. This method is primarily for debugging purposes.

   

6. Restarting the Docker daemon: If you need to restart the Docker service after making configuration changes.

   $ sudo systemctl restart docker

   This command stops and then starts the Docker daemon, applying any configuration changes you’ve made to the Docker daemon configuration files.

Conclusion

Starting and managing the Docker daemon is a fundamental skill for working with containers on Linux. Using systemd commands like “systemctl start docker” and “systemctl enable docker” are the most common methods for modern Linux distributions. Remember that Docker commands require root privileges or a user with sudo access who belongs to the docker group. If you encounter issues, checking the service status and system logs should provide the information needed to resolve them.

Frequently Asked Questions (FAQ)

1. How do I stop the Docker daemon?

   To stop the Docker daemon, use the command sudo systemctl stop docker on systemd-based distributions or sudo service docker stop on SysVinit-based systems. Note that stopping the daemon will terminate all running containers unless you’ve configured them with restart policies.

2. Why does Docker fail to start after installation?

   Common reasons include missing dependencies, conflicts with other container technologies (like podman or LXC), incorrect file permissions, or insufficient system resources. Check the system logs with journalctl -u docker.service to identify specific errors. Make sure your user is in the “docker” group, and that you’ve logged out and back in after adding your user to the group.

3. How can I modify the Docker daemon configuration?

   Docker daemon configuration is managed through the /etc/docker/daemon.json file. You can specify options like the default storage driver, registry mirrors, or network settings in this JSON file. After making changes, restart the daemon with sudo systemctl restart docker to apply them. If the daemon fails to start after configuration changes, check the syntax of your JSON file.

4. Can I run Docker without root privileges?

   Yes, but you need to add your user to the “docker” group. Run sudo usermod -aG docker $USER, then log out and back in for the changes to take effect. The Docker daemon itself runs with root privileges, but users in the docker group can interact with it without using sudo for each command.

5. What’s the difference between ‘docker’ and ‘dockerd’ commands?

   The docker command is the client utility that sends commands to the Docker daemon. The dockerd command directly starts the Docker daemon process. Normal users typically use only the docker client commands, while system administrators might need to work with dockerd for advanced configuration or troubleshooting.