树莓派Docker守护进程异常终止无法启动，bridge网络创建失败求助

Let’s work through your Docker issues step by step—your error messages give us clear clues to what’s going wrong.

1. First, Check the Docker Daemon Status and Logs #

The core problem is the daemon not running, so let’s confirm its state and dig into logs for details:

• Run this to check if the daemon is active:

  sudo service docker status
  

  (If your system uses systemd, use sudo systemctl status docker instead.)
• To view recent daemon logs (critical for spotting crashes or missing dependencies):

  sudo tail -50 /var/log/docker.log
  

  Or for systemd systems:

  sudo journalctl -u docker --since "1 hour ago"
  

2. Fix the "package not installed" Bridge Network Error #

The Error creating default 'bridge' network: package not installed message tells us Docker is missing a critical network dependency: bridge-utils, which provides tools for managing bridge networks.

• Verify if it’s installed:

  dpkg -l | grep bridge-utils
  

• If no results appear, install it immediately:

  sudo apt-get update && sudo apt-get install bridge-utils
  

3. Verify the Docker Socket Permissions #

The read unix connection error often happens when the Docker socket (/var/run/docker.sock) has incorrect permissions, preventing the client from talking to the daemon:

• Check the socket’s ownership:

  ls -l /var/run/docker.sock
  

• If it’s not owned by root:docker, fix it with:

  sudo chown root:docker /var/run/docker.sock
  

4. Ensure the Bridge Kernel Module is Loaded #

Docker relies on the bridge kernel module to create its default network. Let’s make sure it’s active:

• Check if the module is loaded:

  lsmod | grep bridge
  

• If it’s missing, load it manually:

  sudo modprobe bridge
  

• To make it load automatically on boot, add it to your modules list:

  echo "bridge" | sudo tee -a /etc/modules
  

5. Consider Updating (or Reinstalling) Docker #

Your Docker version (1.10.3) is extremely old (released in 2016), and it’s likely incompatible with newer system updates or has known bugs that cause daemon crashes.

• First, stop and uninstall the current version:

  sudo service docker stop
  sudo apt-get purge docker-engine docker.io
  

• Then install a more recent (but still compatible with your 4.1 kernel) version of Docker for ARM. For Raspbian, you can use the official Docker repo tailored for ARM devices—make sure to pick a release that supports your kernel version (look for releases from 2019-2020, which should work with 4.1.x).

After completing these steps, try restarting the Docker daemon:

sudo service docker start

Then run docker version again to confirm both client and daemon are working.

内容的提问来源于stack exchange，提问作者ePascoal