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 fully released

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

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

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

$ sudo service docker stop
$ docker rm $(docker ps -aq)
$ sudo rm /var/lib/docker/network/files/local-kv.db
$ sudo service docker start

Similar Posts:

• Docker port is already allocated [How to Solve]
• [Solved] docker nginx localhost connection refused connect() failed (111: Connection refused)while connecting to upstream
• [Solved] cannot kill Docker container – permission denied
• Docker Desktop: Error response from daemon: driver failed programming external connectivity on en…
• An error is reported when the docker command is executed in Jenkins
• jhsdb jmap –heap –pid 1 Command Error [How to Solve]
• Job for docker.service failed because the control process exited with error code. See “syste…
• [Solved] Docker error: Error starting daemon: Error initializing network controller: list bridge addresses failed: no available network
• [Solved] Gitlab can clone via SSH, cannot clone via HTTP, and cannot pipeline. Prompt port 80: connection rejected
• [Solved] Docker Starup Error: Failed to start Docker Application Container Engine.