• Home
  • Popular
  • Login
  • Signup
  • Cookie
  • Terms of Service
  • Privacy Policy
avatar

Posted by User Bot


30 Nov, 2024

Updated at 13 Dec, 2024

Failed to Start/Connect to Daemon

I tried to google and search the forums for help but to no avail. I’m not exactly sure where to ask in the forums but I thought I might as well take a shot at asking here.

My docker-compose installation has caused encountered some problems and I am unable to use any of the apps I’ve installed using it (immich, PaperMC)

Here is my “docker info” output:

Client: Docker Engine - Community
 Version:    27.3.1
 Context:    default
 Debug Mode: false
 Plugins:
  buildx: Docker Buildx (Docker Inc.)
    Version:  v0.17.1
    Path:     /usr/libexec/docker/cli-plugins/docker-buildx
  compose: Docker Compose (Docker Inc.)
    Version:  v2.29.7
    Path:     /usr/libexec/docker/cli-plugins/docker-compose

Server:
ERROR: Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?
errors pretty printing info

When i use “sudo systemctl status docker”, I get:

docker.service - Docker Application Container Engine
     Loaded: loaded (/usr/lib/systemd/system/docker.service; enabled; preset: enabled)
     Active: active (running) since Thu 2024-11-28 16:53:16 EST; 25min ago
TriggeredBy: ● docker.socket
       Docs: https://docs.docker.com
   Main PID: 1764 (dockerd)
      Tasks: 10
     Memory: 104.0M (peak: 105.5M)
        CPU: 844ms
     CGroup: /system.slice/docker.service
             └─1764 /usr/bin/dockerd -H fd:// --containerd=/run/containerd/containerd.sock

Nov 28 16:53:02 server-name dockerd[1764]: time="2024-11-28T16:53:02.573588887-05:00" level=info msg="Starting up"
Nov 28 16:53:02 server-name dockerd[1764]: time="2024-11-28T16:53:02.697210418-05:00" level=info msg="detected 127.0.0.53 nameserver, assuming systemd-resolved, so using resolv.conf: /run/systemd/resolve/re>
Nov 28 16:53:07 server-name dockerd[1764]: time="2024-11-28T16:53:07.720236511-05:00" level=info msg="[graphdriver] using prior storage driver: overlay2"
Nov 28 16:53:08 server-name dockerd[1764]: time="2024-11-28T16:53:08.009140081-05:00" level=info msg="Loading containers: start."
Nov 28 16:53:09 server-name dockerd[1764]: time="2024-11-28T16:53:09.949762334-05:00" level=info msg="Default bridge (docker0) is assigned with an IP address 172.17.0.0/16. Daemon option --bip can be used t>
Nov 28 16:53:10 server-name dockerd[1764]: time="2024-11-28T16:53:10.450479843-05:00" level=info msg="Loading containers: done."
Nov 28 16:53:16 server-name dockerd[1764]: time="2024-11-28T16:53:16.237915946-05:00" level=info msg="Docker daemon" commit=41ca978 containerd-snapshotter=false storage-driver=overlay2 version=27.3.1
Nov 28 16:53:16 server-name dockerd[1764]: time="2024-11-28T16:53:16.277573270-05:00" level=info msg="Daemon has completed initialization"
Nov 28 16:53:16 server-name dockerd[1764]: time="2024-11-28T16:53:16.609976815-05:00" level=info msg="API listen on /run/docker.sock"
Nov 28 16:53:16 server-name systemd[1]: Started docker.service - Docker Application Container Engine.

Here is the output for "sudo systemctl status docker.socket:

docker.socket - Docker Socket for the API
     Loaded: loaded (/usr/lib/systemd/system/docker.socket; enabled; preset: enabled)
     Active: active (running) since Thu 2024-11-28 16:51:55 EST; 33min ago
   Triggers: ● docker.service
     Listen: /run/docker.sock (Stream)
      Tasks: 0 (limit: 14237)
     Memory: 0B (peak: 256.0K)
        CPU: 701us
     CGroup: /system.slice/docker.socket

Nov 28 16:51:55 server-name systemd[1]: Starting docker.socket - Docker Socket for the API...
Nov 28 16:51:55 server-name systemd[1]: Listening on docker.socket - Docker Socket for the API.

Here is the output for “sudo dockerd -D -l debug”:

INFO[2024-11-28T17:27:16.049588375-05:00] Starting up
failed to start daemon, ensure docker is not running or delete /var/run/docker.pid: process with PID 1764 is still running

I’ve tried uninstalled docker-compose but I still get the same issue and I’ve tried running “dockerd”, “sudo systemctl docker start”, and “sudo service docker restart”

1 post - 1 participant

Read full topic