Ошибка daemon сервиса поставщика

Dharman♦

30.4k22 gold badges84 silver badges132 bronze badges

Just in case someone else needs this. As @Jmons pointed out it was a weird networking issue. So I solved this by forcing a removal

docker network disconnect --force bridge qc.T8

A

answered May 2, 2017 at 22:08

TLDR: restart your docker daemon or restart your docker-machine (if you’re using that e.g. on a mac).

Edit: As there are more recent posts below, they answer the question better then mine. The Network adapter is stuck on the daemon. I’m updating mine as its possibly ‘on top’ of the list and people might not scroll down.

1. Restarting your docker daemon / docker service / docker-machine is the easiest answer.

2. the better answer (via Shalabh Negi):

docker network inspect <network name>
docker network disconnect <network name> <container id/ container name>

This is also faster in real time if you can find the network as restarting the docker machine/demon/service in my experience is a slow thing. If you use that, please scroll down and click +1 on their answer.

So the problem is probably your network adapter (virtual, docker thing, not real): have a quick peek at this: https://github.com/moby/moby/issues/23302.

To prevent it happening again is a bit tricky. It seems there may be an issue with docker where a container exits with a bad status code (e.g. non-zero) that holds the network open. You can’t then start a new container with that endpoint.

answered May 2, 2017 at 18:14

docker network inspect <network name>
docker network disconnect <network name> <container id/ container name>

You can also try doing:

docker network prune
docker volume prune
docker system prune 

these commands will help clearing zombie containers, volume and network.
When no command works then do

sudo service docker restart

your problem will be solved

answered Oct 8, 2019 at 12:43

answered Nov 11, 2019 at 12:36

lac_devlac_dev

1,31614 silver badges20 bronze badges

You could try seeing if there’s any network with that container name by running:

docker network ls

If there is, copy the network id then go on to remove it by running:

docker network rm network-id

answered Aug 18, 2022 at 13:40

Even reboot did not help in my case. It turned out that port 80 to be assigned by the nginx container automatically was in use, even after reboot. How come?

root@IONOS_2: /root/2_proxy # netstat -tlpn
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address           Foreign Address         State       PID/Program name
tcp        0      0 0.0.0.0:873             0.0.0.0:*               LISTEN      1378/rsync
tcp        0      0 0.0.0.0:5355            0.0.0.0:*               LISTEN      1565/systemd-resolv
tcp        0      0 0.0.0.0:80              0.0.0.0:*               LISTEN      1463/nginx: master
tcp        0      0 0.0.0.0:22              0.0.0.0:*               LISTEN      1742/sshd
tcp6       0      0 :::2377                 :::*                    LISTEN      24139/dockerd
tcp6       0      0 :::873                  :::*                    LISTEN      1378/rsync
tcp6       0      0 :::7946                 :::*                    LISTEN      24139/dockerd
tcp6       0      0 :::5355                 :::*                    LISTEN      1565/systemd-resolv
tcp6       0      0 :::21                   :::*                    LISTEN      1447/vsftpd
tcp6       0      0 :::22                   :::*                    LISTEN      1742/sshd
tcp6       0      0 :::5000                 :::*                    LISTEN      24139/dockerd

No idea what nginx: master means or where it came from. And indeed 1463 is the PID:

root@IONOS_2: /root/2_proxy # ps aux | grep "nginx"
root       1463  0.0  0.0  43296   908 ?        Ss   00:53   0:00 nginx: master process /usr/sbin/nginx
root       1464  0.0  0.0  74280  4568 ?        S    00:53   0:00 nginx: worker process
root      30422  0.0  0.0  12108  1060 pts/0    S+   01:23   0:00 grep --color=auto nginx

So I tried this:

root@IONOS_2: /root/2_proxy # kill 1463

root@IONOS_2: /root/2_proxy # ps aux | grep "nginx"
root      30783  0.0  0.0  12108   980 pts/0    S+   01:24   0:00 grep --color=auto nginx

And the problem was gone.

answered Jun 6, 2020 at 0:48