Skip to main content ↑ ↓
Topic solved
This topic has been marked as solved and requires no further attention.
Topic: getting error with docker daemon (Read 373 times) previous topic - next topic
0 Members and 2 Guests are viewing this topic.

getting error with docker daemon

I installed these

world/docker 1:24.0.5-1 [installed]
    Pack, ship and run any application as a lightweight container

world/docker-runit 20220411-2 (runit-galaxy) [installed]
    Runit service script for docker

Code: [Select]

sudo ln -s /etc/runit/sv/docker /etc/runit/runsvdir/default/

sudo sv status docker
down: docker: 1s, normally up, want up; run: log: (pid 29104) 1490s

ps auxxxwwfff  | grep docker
root     29103  0.1  0.0   2348  1380 ?        Ss   03:27   0:01  \_ runsv docker
root     29104  0.0  0.0   2496  1124 ?        S    03:27   0:00      \_ svlogd -tt /var/log/docker
_garp     9412  0.0  0.0   6552  2560 pts/0    S+   03:58   0:00      \_ grep --colour=auto docker


Code: [Select]
docker ps
Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon run

logs dont contain anything,
please guide me, I think I messed up something

Re: getting error with docker daemon

Reply #1 –
Does it give the same message right after a reboot?

Re: getting error with docker daemon

Reply #2 –
oh it works now after reboot,  but I dont understand why reboot was required for this.

Code: [Select]
sudo sv status  docker
run: docker: (pid 1645) 288s; run: log: (pid 1642) 288s


2023-09-25_22:53:34.06469 time="2023-09-26T04:23:34.064674573+05:30" level=info msg="Docker daemon" commit=a61e2b4c9c graphdriver=overlay2 version=24.0.5
2023-09-25_22:53:34.06480 time="2023-09-26T04:23:34.064779545+05:30" level=info msg="Daemon has completed initialization"
2023-09-25_22:53:34.09461 time="2023-09-26T04:23:34.094567552+05:30" level=info msg="API listen on /var/run/docker.sock"

thank you sir

Re: getting error with docker daemon

Reply #3 –
I run into this problem with Docker too. And that's on open-rc. It's likely caused by updating the kernel without rebooting the system. Once the service starts, it's fine.