blocks|key|395589|text|根据针对windows+https://github.com/docker/for-win/issues/3171的Docker问题：|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|395590|您可能在命令netsh+interface+ipv4+show+excludedportrange+protocol=tcp的任何排除端口范围内都有该端口。|style|CODE|395591|您可以使用上述票据中提到的解决方案。|395592|禁用超级v(这将需要几次重新启动)
dism.exe+/Online+/Disable-Feature:Microsoft-Hyper-V|ordered-list-item|395593|完成所有所需的重新启动后，保留您想要的端口，这样hyper-v就不会保留它。
netsh+int+ipv4+add+excludedportrange+protocol=tcp+startport=50070+numberofports=1|395594|重新启用hyper-V+(这需要重新启动几次)
dism.exe+/Online+/Enable-Feature:Microsoft-Hyper-V+/All|395595|entityMap|0|LINK|mutability|MUTABLE|url|https://github.com/docker/for-win/issues/3171^0|C|19|0|0|6|1K|0|0|I|1F|0|13|29|0|O|1J|0^^$0|@$1|2|3|4|5|6|7|Y|8|@]|9|@$A|Z|B|10|1|11]]|C|$]]|$1|D|3|E|5|6|7|12|8|@$A|13|B|14|F|G]]|9|@]|C|$]]|$1|H|3|I|5|6|7|15|8|@]|9|@]|C|$]]|$1|J|3|K|5|L|7|16|8|@$A|17|B|18|F|G]]|9|@]|C|$]]|$1|M|3|N|5|L|7|19|8|@$A|1A|B|1B|F|G]]|9|@]|C|$]]|$1|O|3|P|5|L|7|1C|8|@$A|1D|B|1E|F|G]]|9|@]|C|$]]|$1|Q|3|-4|5|6|7|1F|8|@]|9|@]|C|$]]]|R|$S|$5|T|U|V|C|$W|X]]]]

As per Docker issue for windows <a href="https://github.com/docker/for-win/issues/3171" rel="noreferrer">https://github.com/docker/for-win/issues/3171</a> :
You might have that port in any of the excluded port ranges of command <code>netsh interface ipv4 show excludedportrange protocol=tcp</code>
You can use solution mentioned in the above ticket.
<ol>
<li>Disable hyper-v (which will required a couple of restarts)
<code>dism.exe /Online /Disable-Feature:Microsoft-Hyper-V</code>
</li>
<li>After finishing all the required restarts, reserve the port you want so hyper-v doesn't reserve it back
<code>netsh int ipv4 add excludedportrange protocol=tcp startport=50070 numberofports=1</code>
</li>
<li>Re-Enable hyper-V (which will require a couple of restart)
<code>dism.exe /Online /Enable-Feature:Microsoft-Hyper-V /All</code>
</li>
</ol>

blocks|key|394699|text|这解决方案帮助我：|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|394700|net+stop+winnat
docker+start+container_name
net+start+winnat|code-block|syntax|javascript|394701|entityMap|0|LINK|mutability|MUTABLE|url|https://github.com/docker/for-win/issues/3171#issuecomment-739740248^0|0|1|0|0|0^^$0|@$1|2|3|4|5|6|7|Q|8|@]|9|@$A|R|B|S|1|T]]|C|$]]|$1|D|3|E|5|F|7|U|8|@]|9|@]|C|$G|H]]|$1|I|3|-4|5|6|7|V|8|@]|9|@]|C|$]]]|J|$K|$5|L|M|N|C|$O|P]]]]

<a href="https://github.com/docker/for-win/issues/3171#issuecomment-739740248" rel="noreferrer">This</a> solution helped me:
<pre><code>net stop winnat
docker start container_name
net start winnat
</code></pre>

blocks|key|2646340|text|我这样做是为了阻止tcp进程=>。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2646341|net停止winnat|unordered-list-item|2646342|net启动winnat|2646343|这样，繁忙的端口操作就终止了。|2646344|这对我有用。|2646345|entityMap^0|0|0|0|0|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|D|7|O|8|@]|9|@]|A|$]]|$1|G|3|H|5|6|7|P|8|@]|9|@]|A|$]]|$1|I|3|J|5|6|7|Q|8|@]|9|@]|A|$]]|$1|K|3|-4|5|6|7|R|8|@]|9|@]|A|$]]]|L|$]]

I did this to stop tcp processes =&gt;
<ul>
<li>net stop winnat</li>
<li>net start winnat</li>
</ul>
In this way, the busy port operation is terminated.
This worked for me.

blocks|key|1261095|text|重新启动winnat不是一个好主意。根本原因是Windows的某些端口被动态保留，即使它们没有被占用。此命令可用于求解。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1261096|netsh+int+ipv4+set+dynamic+tcp+start=49152+num=16384
netsh+int+ipv6+set+dynamic+tcp+start=49152+num=16384|code-block|syntax|javascript|1261097|本文将对其进行详细解释，并建议您看一看：|1261098|完全解决了由于端口绑定导致的码头集装箱在Windows+10上运行的问题|1261099|entityMap|0|LINK|mutability|MUTABLE|url|https://medium.com/@sevenall/completely-solve-the-problem-of-docker-containers-not-starting-or-running-on-windows-10-due-to-port-57f16ed6143^0|4|6|0|0|0|0|10|0|0^^$0|@$1|2|3|4|5|6|7|W|8|@$9|X|A|Y|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|Z|8|@]|D|@]|E|$I|J]]|$1|K|3|L|5|6|7|10|8|@]|D|@]|E|$]]|$1|M|3|N|5|6|7|11|8|@]|D|@$9|12|A|13|1|14]]|E|$]]|$1|O|3|-4|5|6|7|15|8|@]|D|@]|E|$]]]|P|$Q|$5|R|S|T|E|$U|V]]]]

Restarting <code>winnat</code> is not a good idea. The root cause is that some ports of Windows are dynamically reserved, even though they are not occupied. This command can be used to solve.
<pre><code>netsh int ipv4 set dynamic tcp start=49152 num=16384
netsh int ipv6 set dynamic tcp start=49152 num=16384
</code></pre>
This article explains it in detail, and I recommend taking a look at it: 
<a href="https://medium.com/@sevenall/completely-solve-the-problem-of-docker-containers-not-starting-or-running-on-windows-10-due-to-port-57f16ed6143" rel="nofollow noreferrer">Completely solve the problem of docker containers running on Windows 10 due to port binding</a>

blocks|key|2646361|text|当我的VPN连接处于活动状态时，我遇到了这种情况。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2646362|您可以暂时断开VPN连接，然后启动docker+container，然后再回连接到VPN。|offset|length|style|CODE|2646363|entityMap^0|0|H|G|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|$]]

I faced with this situation when my VPN connection is active. 
you can temporarily disconnect your VPN connection, after that start your <code>docker container</code>, and go back and connect to your VPN again

blocks|key|1261008|text|在我的本地机器上，Desktop和Debian/Ubuntu作为默认发行版启用了类似的问题(WSL2是所有人的标准版本)。我是怎么解决的|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1261009|码头设置禁用“登录时启动码头桌面”|unordered-list-item|1261010|重新启动Windows|1261011|首次启动Debian/Ubuntu|1261012|然后启动码头桌面|1261013|entityMap^0|0|0|0|0|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|D|7|O|8|@]|9|@]|A|$]]|$1|G|3|H|5|D|7|P|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|Q|8|@]|9|@]|A|$]]|$1|K|3|-4|5|6|7|R|8|@]|9|@]|A|$]]]|L|$]]

On my local machine had similar issue with Docker Desktop and integration enabled with Debian/Ubuntu set as default distro (WSL2 as standard to all). How I solved:
<ul>
<li>Docker settings disabled &quot;Start Docker Desktop when you log in&quot;</li>
<li>Restarting Windows</li>
<li>First starting Debian/Ubuntu</li>
<li>Then start Docker Desktop</li>
</ul>

blocks|key|2646473|text|尝试重新启动“主机网络服务”|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2646474|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|$]]

Try restarting &quot;Host Network Service&quot;

blocks|key|2646498|text|这通常是由Windows+NAT驱动程序(winnat)引起的，停止并重新启动该服务可能会解决问题。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2646499|以管理员身份打开shell，并键入以下命令：|2646500|网停温纳特。|ordered-list-item|2646501|码头开始..。|2646502|net启动winnat|2646503|entityMap^0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|N|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|O|8|@]|9|@]|A|$]]|$1|G|3|H|5|F|7|P|8|@]|9|@]|A|$]]|$1|I|3|J|5|F|7|Q|8|@]|9|@]|A|$]]|$1|K|3|-4|5|6|7|R|8|@]|9|@]|A|$]]]|L|$]]

This is often caused by the Windows NAT Driver (winnat), stopping and restarting that service may resolve the issue.
open shell as administrator, and types those commands:
<ol>
<li>net stop winnat.</li>
<li>docker start ...</li>
<li>net start winnat</li>
</ol>

blocks|key|1261214|text|***net+stop+winnat
docker+start+container_name
net+start+winnat***|type|code-block|depth|inlineStyleRanges|entityRanges|data|syntax|javascript|1261215|用cmd写这篇文章对我来说很好，谢谢这么多的评论员给出了解决方案。|unstyled|1261216|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$B|C]]|$1|D|3|E|5|F|7|J|8|@]|9|@]|A|$]]|$1|G|3|-4|5|F|7|K|8|@]|9|@]|A|$]]]|H|$]]

<pre><code>***net stop winnat
docker start container_name
net start winnat***
</code></pre>
writing this in cmd worked well for me, thank you so much commentators for the solution.

I am trying to start a docker container with the below command.
<pre><code>docker run -it -p 50070:50070 -p 8088:8088 -p 8080:8080 suhothayan/hadoop-spark-pig-hive:2.9.2 bash
</code></pre>
It ended up with the following error.
<blockquote>
docker: error response from daemon: Ports are not available: listen tcp 0.0.0.0/50070: bind: An attempt was made to access a socket in a way forbidden by its access permissions.
</blockquote>
As I understand, the error has occurred as the port 50070 is used by another process. I've tried to identify the process in order to kill that with the below command in the command prompt, but it does not give an output nor an error.
<pre><code>netstat -ano | findstr :50080
</code></pre>

Ports are not available: listen tcp 0.0.0.0/50070: bind: An attempt was made to access a socket in a way forbidden by its access permissions

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

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

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

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

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

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

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

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋 

腾讯云代码助手

CODING DevOps

Cloud Studio

SDK中心

API中心

命令行工具

我试图用下面的命令启动一个码头容器。docker run -it -p 50070:50070 -p 8088:8088 -p 8080:8080 suhothayan/hadoop-spark-pig-hive:2.9.2 bash它最终导致了以下错误。docker:来自守护进程的错误响应:端口不可用:ListTCP0.0.0/50070: bind:尝试以其访问权限禁止的方式访问套接字。据我所

问端口不可用:ListTCP0.0.0.0/50070: bind:尝试以其访问权限禁止的方式访问套接字
EN

回答 9

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问端口不可用:ListTCP0.0.0.0/50070: bind:尝试以其访问权限禁止的方式访问套接字EN

回答 9

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问端口不可用:ListTCP0.0.0.0/50070: bind:尝试以其访问权限禁止的方式访问套接字
EN