Shulou(Shulou.com)06/01 Report--

This article introduces Bind for 0.0.0.0:80 failed: port is already allocated. What is the solution? The content is very detailed. Interested friends can refer to it for reference. I hope it can help you.

0.0.0.0:443 failed: port is already allocated

Bind for 0.0.0.0:80 failed: port is already allocated.

In a word, the port occupied by the container has not been completely released

Check the process and find that the container is not running, but docker-proxy is still bound to the port:

ps -aux | grep -v grep | grep docker-proxy

Stop the doker process, delete all containers, delete local-kv.db, and start docker.

$ sudo service docker stop$ docker rm $(docker ps -aq)$ sudo rm /var/lib/docker/network/files/local-kv.db$ sudo service docker start Bind for 0.0.0: 80 failed: port is already allocated. If you think the article is good, you can share it so that more people can see it.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.