blocks|key|1592010|text|在启动使用相同端口的新容器之前，需要确保您启动的上一个容器已被杀死。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1592011|docker+container+ls
docker+rm+-f+<container-name>|code-block|syntax|javascript|1592012|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

You need to make sure that the previous container you launched is killed, before launching a new one that uses the same port.

<pre><code>docker container ls
docker rm -f &lt;container-name&gt;
</code></pre>

blocks|key|2883808|text|为了向IgorBeaz致敬，您需要停止运行当前容器。为此，您将了解当前容器ID：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2883809|$+docker+container+ls|code-block|syntax|javascript|2883810|你会得到这样的东西：|2883811|CONTAINER+ID++++++++IMAGE+++++++++++++++COMMAND+++++++++++++CREATED+++++++++++++STATUS++++++++++++++PORTS++++++++++++++++++NAMES
12a32e8928ef++++++++friendlyhello+++++++"python+app.py"+++++51+seconds+ago++++++Up+50+seconds+++++++0.0.0.0:4000->80/tcp+++romantic_tesla+++|2883812|然后通过以下方式阻止容器：|2883813|$+docker+stop+12a32e8928ef|2883814|最后，您尝试做您想做的事情，例如：|2883815|$+docker+run+-p+4000:80+friendlyhello|2883816|entityMap^0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|U|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|V|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|W|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|X|8|@]|9|@]|A|$E|F]]|$1|K|3|L|5|6|7|Y|8|@]|9|@]|A|$]]|$1|M|3|N|5|D|7|Z|8|@]|9|@]|A|$E|F]]|$1|O|3|P|5|6|7|10|8|@]|9|@]|A|$]]|$1|Q|3|R|5|D|7|11|8|@]|9|@]|A|$E|F]]|$1|S|3|-4|5|6|7|12|8|@]|9|@]|A|$]]]|T|$]]

Paying tribute to IgorBeaz, you need to stop running the current container. For that you are going to know current CONTAINER ID:

<pre><code>$ docker container ls
</code></pre>

You get something like:

<pre><code>CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
12a32e8928ef friendlyhello "python app.py" 51 seconds ago Up 50 seconds 0.0.0.0:4000-&gt;80/tcp romantic_tesla 
</code></pre>

Then you stop the container by:

<pre><code>$ docker stop 12a32e8928ef
</code></pre>

Finally you try to do what you wanted to do, for example:

<pre><code>$ docker run -p 4000:80 friendlyhello
</code></pre>

blocks|key|2883873|text|以上两个答案是正确的，但对我不起作用。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2883874|我一直看到docker+container+ls的空白，如下面所示|ordered-list-item|offset|length|style|CODE|2883875|📷|atomic|2883876|​|2883877|然后我试了一下，docker+container+ls+-a，然后它显示了以前退出和运行的所有进程。|2883878|那么docker+stop+<container+id>或docker+container+stop+<container+id>就不起作用了|2883879|然后我尝试了docker+rm+-f+<container+id>，它成功了。|2883880|在这里，我尝试了docker+container+ls+-a，但是这个过程没有出现。|2883881|entityMap|0|IMAGE|mutability|IMMUTABLE|imageUrl|https://developer.qcloudimg.com/http-save/yehe-900000/c7913fa86fd8381102ca17bd70b62650.png|imageAlt^0|0|5|J|0|0|1|0|0|0|8|M|0|2|Q|T|10|0|6|R|0|8|M|0^^$0|@$1|2|3|4|5|6|7|14|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|15|8|@$E|16|F|17|G|H]]|9|@]|A|$]]|$1|I|3|J|5|K|7|18|8|@]|9|@$E|19|F|1A|1|1B]]|A|$]]|$1|L|3|M|5|6|7|1C|8|@]|9|@]|A|$]]|$1|N|3|O|5|D|7|1D|8|@$E|1E|F|1F|G|H]]|9|@]|A|$]]|$1|P|3|Q|5|D|7|1G|8|@$E|1H|F|1I|G|H]|$E|1J|F|1K|G|H]]|9|@]|A|$]]|$1|R|3|S|5|D|7|1L|8|@$E|1M|F|1N|G|H]]|9|@]|A|$]]|$1|T|3|U|5|D|7|1O|8|@$E|1P|F|1Q|G|H]]|9|@]|A|$]]|$1|V|3|-4|5|6|7|1R|8|@]|9|@]|A|$]]]|W|$X|$5|Y|Z|10|A|$11|12|13|-4]]]]

Above two answers are correct but didn't work for me. 

<ol>
<li>I kept on seeing blank like below for <code>docker container ls</code><a href="https://i.stack.imgur.com/YDaMQ.png" rel="noreferrer"><img src="https://i.stack.imgur.com/YDaMQ.png" alt="enter image description here"></a></li>
<li>then I tried, <code>docker container ls -a</code> and after that it showed all the process previously exited and running.</li>
<li>Then <code>docker stop &lt;container id&gt;</code> or <code>docker container stop &lt;container id&gt;</code> didn't work </li>
<li>then I tried <code>docker rm -f &lt;container id&gt;</code> and it worked.</li>
<li>Now at this I tried <code>docker container ls -a</code> and this process wasn't present.</li>
</ol>

blocks|key|2922060|text|把集装箱停下来对我也没用。我改变了docker-compose.yml的端口。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|2922061|entityMap^0|H|I|0^^$0|@$1|2|3|4|5|6|7|H|8|@$9|I|A|J|B|C]]|D|@]|E|$]]|$1|F|3|-4|5|6|7|K|8|@]|D|@]|E|$]]]|G|$]]

Stopping the container didn't work for me either. I changed the port in <code>docker-compose.yml</code>.

blocks|key|2922097|text|对于任何有docker-compose问题的人来说。当您有多个具有类似服务的项目(即不同文件夹)时，您需要在其他每个项目中运行docker-compose+stop。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|2922098|entityMap^0|5|E|1R|J|0^^$0|@$1|2|3|4|5|6|7|H|8|@$9|I|A|J|B|C]|$9|K|A|L|B|C]]|D|@]|E|$]]|$1|F|3|-4|5|6|7|M|8|@]|D|@]|E|$]]]|G|$]]

For anyone having this problem with <code>docker-compose</code>. 
When you have more than one project (i.e. in different folders) with similar services you need to run <code>docker-compose stop</code> in each of your other projects.

blocks|key|2922115|text|为了解决这个问题，我在docker-compose上也遇到了同样的问题：|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|2922116|被杀码头-代理程序e|ordered-list-item|2922117|重新启动码头|2922118|重新启动船坞-写作|2922119|entityMap^0|B|E|0|0|0|0^^$0|@$1|2|3|4|5|6|7|O|8|@$9|P|A|Q|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|R|8|@]|D|@]|E|$]]|$1|I|3|J|5|H|7|S|8|@]|D|@]|E|$]]|$1|K|3|L|5|H|7|T|8|@]|D|@]|E|$]]|$1|M|3|-4|5|6|7|U|8|@]|D|@]|E|$]]]|N|$]]

I have had same problem with <code>docker-compose</code>, to fix it:
<ol>
<li>Killed docker-proxy processe</li>
<li>Restart docker</li>
<li>Start docker-compose again</li>
</ol>

blocks|key|2922149|text|我就这样解决了：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2922150|首先，我停止了所有正在运行的容器：|2922151|docker-compose+down|code-block|syntax|javascript|2922152|然后我执行了一个lsof命令来使用端口查找进程(对我来说是端口9000)|offset|length|style|CODE|2922153|sudo+lsof+-i+-P+-n+%7C+grep+9000|2922154|最后，我“扼杀”了这个过程(在我的例子中，它是一个VSCode扩展)：|2922155|kill+-9+<process+id>|2922156|entityMap^0|0|0|0|8|4|0|0|0|0^^$0|@$1|2|3|4|5|6|7|W|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|X|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|Y|8|@]|9|@]|A|$G|H]]|$1|I|3|J|5|6|7|Z|8|@$K|10|L|11|M|N]]|9|@]|A|$]]|$1|O|3|P|5|F|7|12|8|@]|9|@]|A|$G|H]]|$1|Q|3|R|5|6|7|13|8|@]|9|@]|A|$]]|$1|S|3|T|5|F|7|14|8|@]|9|@]|A|$G|H]]|$1|U|3|-4|5|6|7|15|8|@]|9|@]|A|$]]]|V|$]]

I solved it this way:

First, I stopped all running containers:

<pre><code>docker-compose down
</code></pre>

Then I executed a <code>lsof</code> command to find the process using the port (for me it was port 9000)

<pre><code>sudo lsof -i -P -n | grep 9000
</code></pre>

Finally, I "killed" the process (in my case, it was a VSCode extension):

<pre><code>kill -9 &lt;process id&gt;
</code></pre>

blocks|key|2922170|text|docker+ps将显示在码头上运行的集装箱列表。找到在您需要的端口上运行的一个，并记下它的PID。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|2922171|使用以下命令停止并删除该容器：|2922172|docker+stop+PID
docker+rm+PID|code-block|syntax|javascript|2922173|现在运行docker-compose+up，您的服务应该在释放所需端口时运行。|2922174|entityMap^0|0|9|0|0|0|4|H|0^^$0|@$1|2|3|4|5|6|7|Q|8|@$9|R|A|S|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|T|8|@]|D|@]|E|$]]|$1|H|3|I|5|J|7|U|8|@]|D|@]|E|$K|L]]|$1|M|3|N|5|6|7|V|8|@$9|W|A|X|B|C]]|D|@]|E|$]]|$1|O|3|-4|5|6|7|Y|8|@]|D|@]|E|$]]]|P|$]]

<code>docker ps</code> will reveal the list of containers running on docker. Find the one running on your needed port and note down its PID.
Stop and remove that container using following commands:
<pre><code>docker stop PID
docker rm PID
</code></pre>
Now run <code>docker-compose up</code> and your services should run as you have freed the needed port.

blocks|key|2883991|text|我尝试了以上所有的答案，但没有一个有效，在我的例子中，甚至docker+container+ls都没有显示任何容器正在运行。看起来，这个问题是由于码头代理仍然在使用端口，尽管没有容器在运行。在我的例子中，我使用的是ubuntu。下面是我尝试解决问题的方法，只需运行以下两个命令：|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|2883992|sudo+service+docker+stop
sudo+rm+-f+/var/lib/docker/network/files/local-kv.db|code-block|syntax|javascript|2883993|entityMap^0|T|J|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@$9|N|A|O|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|P|8|@]|D|@]|E|$I|J]]|$1|K|3|-4|5|6|7|Q|8|@]|D|@]|E|$]]]|L|$]]

I tried all the above answers, none of them worked, in my case even <code>docker container ls</code> doesn't show any container running. It looks like the problem is due to the fact that the docker proxy is still using ports although there are no containers running. In my case I was using ubuntu. Here's what I tried and got the problem solved, just run the following two commands:
<pre><code>sudo service docker stop
sudo rm -f /var/lib/docker/network/files/local-kv.db
</code></pre>

blocks|key|2884010|text|它可能与docker-compose.yml和docker-compose.override.yml中指定的相同端口或使用环境变量显式指定的相同端口发生冲突。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|2884011|我有一个docker-compose.yml，它的端口位于使用环境变量指定的容器上，而docker-compose.override.yml具有相同端口之一的显式指定。很明显，码头工人试图在同一个集装箱上打开两个。docker+container+ls+-a没有列出，因为容器无法启动并列出端口。|2884012|entityMap^0|4|I|N|R|0|4|I|17|R|2Z|M|0^^$0|@$1|2|3|4|5|6|7|J|8|@$9|K|A|L|B|C]|$9|M|A|N|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|O|8|@$9|P|A|Q|B|C]|$9|R|A|S|B|C]|$9|T|A|U|B|C]]|D|@]|E|$]]|$1|H|3|-4|5|6|7|V|8|@]|D|@]|E|$]]]|I|$]]

It might be a conflict with the same port specified in <code>docker-compose.yml</code> and <code>docker-compose.override.yml</code> or the same port specified explicitly and using an environment variable.
I had a <code>docker-compose.yml</code> with ports on a container specified using environment variables, and a <code>docker-compose.override.yml</code> with one of the same ports specified explicitly. Apparently docker tried to open both on the same container. <code>docker container ls -a</code> listed neither because the container could not start and list the ports.

blocks|key|2922220|text|快速修复是​​，一个刚刚重新启动的码头。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2922221|sudo+service+docker+stop|ordered-list-item|offset|length|style|CODE|2922222|sudo+service+docker+start|2922223|entityMap^0|0|0|O|0|0|P|0^^$0|@$1|2|3|4|5|6|7|M|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|N|8|@$E|O|F|P|G|H]]|9|@]|A|$]]|$1|I|3|J|5|D|7|Q|8|@$E|R|F|S|G|H]]|9|@]|A|$]]|$1|K|3|-4|5|6|7|T|8|@]|9|@]|A|$]]]|L|$]]

The quick fix is ​​a just restart docker:
<ol>
<li><code>sudo service docker stop</code></li>
<li><code>sudo service docker start</code></li>
</ol>

blocks|key|2884041|text|在我的情况下，没有程序可以杀死。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2884042|更新码头修复了问题。|2884043|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

In my case, there was no process to kill.
Updating docker fixed the problem.

blocks|key|2884051|text|如果您使用的是，则可以退出Desktop并重新启动它。它帮我解决了这个问题。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2884052|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

If you are using Docker-Desktop, you can quit Docker Desktop and than restart it. It solved the problem for me.

blocks|key|2884116|text|对我来说，没有运行的集装箱，所以没有使用端口9010+(在我的情况下)，但码头仍然抱怨。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2884117|我不想重置我的Docker+(对于Windows)，所以我所做的解决它的简单方法是：|2884118|删除网络(我知道在容器使用此网络之前，该端口为(9010)+docker+network+ls+docker+network+rm+blabla+(or+id)|ordered-list-item|offset|length|style|CODE|2884119|实际上，我使用的是一个新的网络，而不是旧的(+but+)网络，但不应该需要它。|2884120|重新启动码头|2884121|这是唯一适合我的方法。我无法解释，但不知何故，“旧”网络仍然绑定到那个端口(9010)，码头继续“阻塞”它(抱怨)|2884122|entityMap^0|0|0|U|H|1C|W|0|0|0|0^^$0|@$1|2|3|4|5|6|7|S|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|T|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|U|8|@$G|V|H|W|I|J]|$G|X|H|Y|I|J]]|9|@]|A|$]]|$1|K|3|L|5|F|7|Z|8|@]|9|@]|A|$]]|$1|M|3|N|5|F|7|10|8|@]|9|@]|A|$]]|$1|O|3|P|5|6|7|11|8|@]|9|@]|A|$]]|$1|Q|3|-4|5|6|7|12|8|@]|9|@]|A|$]]]|R|$]]

For me the containers where not showing up running, so NOTHING was using port 9010 (in my case) BUT Docker still complained.
I did not want to reset my Docker (for Windows) so what I did to resolve it was simply:
<ol>
<li>Remove the network (I knew that before a container was using this network with the port in question (9010) <code>docker network ls</code> <code>docker network rm blabla (or id)</code></li>
<li>I actually used a new network rather than the old (buggy) one but shouldn't be needed</li>
<li>Restart Docker</li>
</ol>
That was the only way it worked for me. I can't explain it but somehow the &quot;old&quot; network was still bound to that port (9010) and Docker kept on &quot;blocking&quot; it (whinching about it)

blocks|key|2884171|text|在Linux上，您可以运行sudo+netstat+-tulpn来查看当前在该端口上监听的内容。然后，可以选择将该进程或Docker容器配置为绑定到其他端口，以避免冲突。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|2884172|entityMap^0|D|J|0^^$0|@$1|2|3|4|5|6|7|H|8|@$9|I|A|J|B|C]]|D|@]|E|$]]|$1|F|3|-4|5|6|7|K|8|@]|D|@]|E|$]]]|G|$]]

On Linux, you can run <code>sudo netstat -tulpn</code> to see what is currently listening on that port. You can then choose to configure either that process or your Docker container to bind to a different port to avoid the conflict.

blocks|key|1592460|text|当我使用nginx+docker映像时，我还得到了以下错误：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1592461|docker:+Error+response+from+daemon:+driver+failed+programming+external+connectivity+on+endpoint+recursing_knuth+(9186f7d7f523732b99d3510029cde9679f3f3fe7b7eb5f612d54c4aacea58220):+Bind+for+0.0.0.0:8080+failed:+port+is+already+allocated.|code-block|syntax|javascript|1592462|我使用以下命令解决了这个问题：|1592463|$+docker+container+ls
$+docker+stop+[CONTAINER+ID]|1592464|然后，再次运行这个码头容器(像这样)就可以了：|1592465|$+docker+run+-v+$PWD/vueDemo:/usr/share/nginx/html+-p+8080:80+-d+nginx:alpine|1592466|您只需停止前一个码头容器.|offset|length|style|BOLD|1592467|entityMap^0|0|0|0|0|0|0|0|D|0^^$0|@$1|2|3|4|5|6|7|W|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|X|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|Y|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|Z|8|@]|9|@]|A|$E|F]]|$1|K|3|L|5|6|7|10|8|@]|9|@]|A|$]]|$1|M|3|N|5|D|7|11|8|@]|9|@]|A|$E|F]]|$1|O|3|P|5|6|7|12|8|@$Q|13|R|14|S|T]]|9|@]|A|$]]|$1|U|3|-4|5|6|7|15|8|@]|9|@]|A|$]]]|V|$]]

When I used nginx docker image, I also got this error:
<pre><code>docker: Error response from daemon: driver failed programming external connectivity on endpoint recursing_knuth (9186f7d7f523732b99d3510029cde9679f3f3fe7b7eb5f612d54c4aacea58220): Bind for 0.0.0.0:8080 failed: port is already allocated.
</code></pre>
And I solved it using following commands:
<pre><code>$ docker container ls
$ docker stop [CONTAINER ID]
</code></pre>
Then, running this docker container(like this) again is ok:
<pre><code>$ docker run -v $PWD/vueDemo:/usr/share/nginx/html -p 8080:80 -d nginx:alpine
</code></pre>
You just need to stop the previous docker container.

blocks|key|1592489|text|别忘了最简单的办法.|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1592490|重新启动计算机。|blockquote|1592491|我已经尝试了以上的大部分，但仍然无法修复它。然后只有restart+my+Mac，然后一切都恢复正常。|offset|length|style|CODE|1592492|entityMap^0|0|0|Q|E|0^^$0|@$1|2|3|4|5|6|7|M|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|N|8|@]|9|@]|A|$]]|$1|E|3|F|5|6|7|O|8|@$G|P|H|Q|I|J]]|9|@]|A|$]]|$1|K|3|-4|5|6|7|R|8|@]|9|@]|A|$]]]|L|$]]

Don't forget the easiest fix of all....
<blockquote>
Restart your computer.
</blockquote>
I have tried most of the above and still couldn't fix it. Then just <code>restart my Mac</code> and then it's all back to normal.

blocks|key|2884233|text|对我来说，问题是映射同一个端口两次。|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|2884234|由于参数化的docker+run，最终的结果是|CODE|2884235|docker+run+-p+4000:80+-p+4000:80+anibar/get-started:part1|code-block|syntax|javascript|2884236|注意端口4000上的双映射。|2884237|在这种情况下，日志信息不够丰富，因为它没有声明docker+run+i是双映射的原因，并且在命令返回失败之后，端口不再绑定。|2884238|entityMap^0|8|9|0|6|A|0|0|0|N|A|1A|6|1J|7|N|A|0^^$0|@$1|2|3|4|5|6|7|T|8|@$9|U|A|V|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|W|8|@$9|X|A|Y|B|H]]|D|@]|E|$]]|$1|I|3|J|5|K|7|Z|8|@]|D|@]|E|$L|M]]|$1|N|3|O|5|6|7|10|8|@]|D|@]|E|$]]|$1|P|3|Q|5|6|7|11|8|@$9|12|A|13|B|C]|$9|14|A|15|B|C]|$9|16|A|17|B|C]|$9|18|A|19|B|H]]|D|@]|E|$]]|$1|R|3|-4|5|6|7|1A|8|@]|D|@]|E|$]]]|S|$]]

For me, the problem was mapping the same port twice.
Due to a parametric <code>docker run</code>, it ended up being something like
<pre><code>docker run -p 4000:80 -p 4000:80 anibar/get-started:part1
</code></pre>
notice double mapping on port 4000.
The log is not informative enough in this case, as it doesn't state I was the cause of the double mapping, and that the port is no longer bound after the <code>docker run</code> command returns with a failure.

blocks|key|1592563|text|对于仍在寻找解决方案的人，只需确保您已将端口以正确的方式绑定在您的docker-come.yml中。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1592564|它说：-+<EXTERNAL+SERVER+PORT>:<INTERNAL+CONTAINER+PORT>|offset|length|style|CODE|1592565|entityMap^0|0|3|1E|0^^$0|@$1|2|3|4|5|6|7|J|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|K|8|@$D|L|E|M|F|G]]|9|@]|A|$]]|$1|H|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|I|$]]

For anyone still looking for a solution, just make sure you have binded your port the right way round in your docker-compose.yml
It goes:
<code>- &lt;EXTERNAL SERVER PORT&gt;:&lt;INTERNAL CONTAINER PORT&gt;</code>

blocks|key|2922463|text|也有同样的问题。转到Docker以获取并单击“重新启动”。问题解决了。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2922464|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

Had the same problem. Went to Docker for Mac Dashboard and clicked restart. Problem solved.

blocks|key|2884307|text|只需重新启动计算机，就可以重新启动对接服务。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2884308|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

simply restart your computer, so the docker service gets restarted

blocks|key|1592616|text|在linux上'sudo+systemctl重新启动码头‘为我解决了这个问题。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1592617|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

on linux 'sudo systemctl restart docker' solved the issue for me

blocks|key|2884326|text|FOR+WINDOWS;杀死了停靠者使用的每个进程，并在服务上重新启动了对接服务。我的容器现在能用了。这是关于港口仍然在使用的码头，即使你没有使用在那一刻。|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|2884327|entityMap^0|0|C|0^^$0|@$1|2|3|4|5|6|7|H|8|@$9|I|A|J|B|C]]|D|@]|E|$]]|$1|F|3|-4|5|6|7|K|8|@]|D|@]|E|$]]]|G|$]]

FOR WINDOWS;
I killed every process that docker use and restarted the docker service on services. My containers are working now.
It is about ports that is still in use by Docker even though you are not using on that moment.

blocks|key|2884334|text|我的案例是转储XD，我曾两次公开端口80+:D|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2884335|++++++++ports:
++++++++++++-+'${APP_PORT:-80}:80'
++++++++++++-+'${APP_PORT:-8080}:8080'|code-block|syntax|javascript|2884336|定义了APP_PORT，因此80被公开了两次。|2884337|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|K|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|L|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|M|8|@]|9|@]|A|$]]|$1|I|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|J|$]]

my case was dump XD I was exposing port 80 twice :D
<pre><code> ports:
 - '${APP_PORT:-80}:80'
 - '${APP_PORT:-8080}:8080'
</code></pre>
APP_PORT is defined, thus 80 was exposed twice.

blocks|key|2884378|text|我尝试了几乎所有的解决方案，并找到了可能的/可能的原因/解决方案。因此，如果您正在使用traefik或任何其他网络服务器，它们在内部为负载平衡代理提供便利。这，大多数人使用的蓝图，因为它，工作相当好。然后，它将负载控制完全传递给nginx或类似的代理服务器。因此，停止、杀戮(networking+server)或修剪可能没有帮助。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|2884379|traefik的nginx解决方案，|2884380|sudo+/etc/init.d/nginx+stop
#+or
sudo+service+nginx+stop
#+or
sudo+systemctl+stop+nginx|code-block|syntax|javascript|2884381|学分|2884382|entityMap|0|LINK|mutability|MUTABLE|url|https://www.cyberciti.biz/faq/nginx-restart-ubuntu-linux-command/^0|17|7|36|5|3U|H|0|0|7|8|5|0|0|0|2|0|0^^$0|@$1|2|3|4|5|6|7|W|8|@$9|X|A|Y|B|C]|$9|Z|A|10|B|C]|$9|11|A|12|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|13|8|@$9|14|A|15|B|C]|$9|16|A|17|B|C]]|D|@]|E|$]]|$1|H|3|I|5|J|7|18|8|@]|D|@]|E|$K|L]]|$1|M|3|N|5|6|7|19|8|@]|D|@$9|1A|A|1B|1|1C]]|E|$]]|$1|O|3|-4|5|6|7|1D|8|@]|D|@]|E|$]]]|P|$Q|$5|R|S|T|E|$U|V]]]]

I tried almost all solutions and found out the probable/possible reason/solution. So, If you are using <code>traefik</code> or any other networking server, they internally facilitate proxy for load balacing. That, most use the blueprint as it, works pretty fine. It then passes the load control entirely to <code>nginx</code> or similiar proxy servers. So, stopping, killing(<code>networking server</code>) or pruning might not help.
Solution for <code>traefik</code> with <code>nginx</code>,
<pre><code>sudo /etc/init.d/nginx stop
# or
sudo service nginx stop
# or
sudo systemctl stop nginx
</code></pre>
<a href="https://www.cyberciti.biz/faq/nginx-restart-ubuntu-linux-command/" rel="nofollow noreferrer">Credits</a>

I am using docker for the first time and I was trying to implement this -
<a href="https://docs.docker.com/get-started/part2/#tag-the-image" rel="noreferrer">https://docs.docker.com/get-started/part2/#tag-the-image</a>
At one stage I was trying to connect with localhost by this command -
<pre><code>$ curl http://localhost:4000
</code></pre>
which showed this error-
<pre><code>curl: (7) Failed to connect to localhost port 4000: Connection refused
</code></pre>
However, I have solved this by following code -
<pre><code>$ docker-machine ip default
$ curl http://192.168.99.100:4000
</code></pre>
After that everything was going fine, but in the last part, I was trying to run the app by using following line according to the tutorial...
<pre><code>$ docker run -p 4000:80 anibar/get-started:part1
</code></pre>
But, I got this error
<pre><code>C:\Program Files\Docker Toolbox\docker.exe: Error response from daemon: driver failed programming external connectivity on endpoint goofy_bohr (63f5691ef18ad6d6389ef52c56198389c7a627e5fa4a79133d6bbf13953a7c98): Bind for 0.0.0.0:4000 failed: port is already allocated.
</code></pre>

Docker - Bind for 0.0.0.0:4000 failed: port is already allocated

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

我第一次使用了docker，并且我试图实现这个- 。有一段时间，我试图通过这个命令连接本地主机-$ curl http://localhost:4000这表明了这个错误-curl: (7) Failed to connect to localhost port 4000: Connection refused但是，我已...

问Docker -绑定0.0.0.0:4000失败:端口已被分配
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问Docker -绑定0.0.0.0:4000失败:端口已被分配EN