blocks|key|124580|text|更新2019|type|unstyled|depth|inlineStyleRanges|entityRanges|data|124581|正如duct_tape_coder在the+comments中所指出的那样|offset|length|124582|124583|微软has+improved+the+network+options+for+containers和现在的通过改进的命名空间，允许每个pod有多个容器。|blockquote|style|BOLD|124584|124585|124586|124587|理论上(原答案2015年10月)：|124588|Linux主机上没有运行"Windows容器“。|124589|而且Linux容器不会直接在Windows服务器上运行，因为it+relies+on+system+calls+to+a+Linux+kernel。|124590|当然，您可以通过VM在任何Windows计算机上运行这些Linux容器。|124591|这就是docker+toolbox+will+install所说的。|124592|将会有support+for+docker+on+Windows+soon，但这将是用于Windows容器，而不是Linux容器。|124593|Update+2017：是的，LinuxKit允许在Windows平台上通过wrapper+V隔离包装器，通过从构建的最小的linux操作系统来运行Update+2017容器。|124594|这仍然是相同的想法:+linux在Windows上的VM中运行。|124595|这不是部署在Windows服务器上的Linux服务器:仅部署在Windows上的VM中运行的Linux服务器内。|124596|124597|实际上..。(更新2016年12月)|124598|参见"Linux+and+Windows,+living+together,+total+chaos!+(OK,+Kubernetes+1.5)“|124599|124600|+Kubernetes1.5包括对Windows+Server容器(类似于Docker的共享内核模型)和Hyper-V容器(为多租户环境提供更好的隔离)的alpha支持(以更大的延迟为代价)。|124601|124602|最终结果是能够创建单个Kubernetes集群，该集群不仅包括运行Linux容器的Linux节点或运行Windows容器的Windows节点，而且能够并排包含两者，以实现真正的混合体验。|124603|例如，单个服务可以具有使用Windows+Server容器的PODs和使用+containers的其他PODs。|124604|124605|但是：|124606|124607|虽然它看起来功能齐全，但在这个早期版本中确实存在一些限制，包括：|124608|124609|124610|由于其编写方式的依赖性，|124611|The+Kubernetes+master必须仍然在Linux上运行。移植到Windows是有可能的，但目前团队觉得把精力集中在客户端上更好，因为components.|unordered-list-item|124612|There不支持windows中容器的网络覆盖，所以联网仅限于L3。(还有其他解决方案，但它们不是本机可用的。)|124613|124614|Kubernetes+Windows+SIG正在与微软合作来解决这些问题，然而，他们希望通过Kubernetes1.6的早期发布取得进展Windows容器之间的next+year.|124615|Networking更加复杂，因为每个容器都有自己的网络命名空间，所以建议您使用单容器pods++now.|124616|
|124617|Applications在Windows+Server容器中运行可以在Windows支持的任何语言中运行。您可以在.NET容器中运行.NET应用程序，但前提是它们是用Linux编写的。Nano+Server操作系统也支持.NET核心，该操作系统可以部署在Windows+Server容器上。|124618|124619|124620|entityMap|0|LINK|mutability|MUTABLE|url|https://stackoverflow.com/users/5419381/duct-tape-coder|1|https://stackoverflow.com/questions/33190469/linux-machine-with-docker-deploy-windows-container/33190605#comment96408605_33190605|2|https://docs.microsoft.com/en-us/virtualization/windowscontainers/container-networking/architecture|3|https://stackoverflow.com/a/32757109/6309|4|https://www.docker.com/toolbox|5|https://blog.docker.com/2015/08/tp-docker-engine-windows-server-2016/|6|https://thenewstack.io/finally-linux-containers-really-will-run-windows-linuxkit/|7|8|https://www.mirantis.com/blog/linux-windows-living-together-total-chaos-ok-kubernetes-1-5/^0|0|2|F|0|I|C|1|0|0|1H|9|2|1B|2|0|0|0|0|0|0|U|17|3|0|0|3|R|4|0|3|Y|5|0|0|B|6|22|B|7|0|0|0|0|0|3|1X|8|0|0|1|1V|0|0|0|11|B|0|0|0|0|0|0|0|0|0|2C|0|0|1K|0|0|0|2I|0|0|1H|0|0|0|41|0|0|0^^$0|@$1|2|3|4|5|6|7|2W|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|2X|8|@]|9|@$D|2Y|E|2Z|1|30]|$D|31|E|32|1|33]]|A|$]]|$1|F|3|-4|5|6|7|34|8|@]|9|@]|A|$]]|$1|G|3|H|5|I|7|35|8|@$D|36|E|37|J|K]]|9|@$D|38|E|39|1|3A]]|A|$]]|$1|L|3|-4|5|6|7|3B|8|@]|9|@]|A|$]]|$1|M|3|-4|5|6|7|3C|8|@]|9|@]|A|$]]|$1|N|3|-4|5|6|7|3D|8|@]|9|@]|A|$]]|$1|O|3|P|5|6|7|3E|8|@]|9|@]|A|$]]|$1|Q|3|R|5|6|7|3F|8|@]|9|@]|A|$]]|$1|S|3|T|5|6|7|3G|8|@]|9|@$D|3H|E|3I|1|3J]]|A|$]]|$1|U|3|V|5|6|7|3K|8|@]|9|@]|A|$]]|$1|W|3|X|5|6|7|3L|8|@]|9|@$D|3M|E|3N|1|3O]]|A|$]]|$1|Y|3|Z|5|6|7|3P|8|@]|9|@$D|3Q|E|3R|1|3S]]|A|$]]|$1|10|3|11|5|6|7|3T|8|@]|9|@$D|3U|E|3V|1|3W]|$D|3X|E|3Y|1|3Z]]|A|$]]|$1|12|3|13|5|6|7|40|8|@]|9|@]|A|$]]|$1|14|3|15|5|6|7|41|8|@]|9|@]|A|$]]|$1|16|3|-4|5|6|7|42|8|@]|9|@]|A|$]]|$1|17|3|18|5|6|7|43|8|@]|9|@]|A|$]]|$1|19|3|1A|5|6|7|44|8|@]|9|@$D|45|E|46|1|47]]|A|$]]|$1|1B|3|-4|5|6|7|48|8|@]|9|@]|A|$]]|$1|1C|3|1D|5|I|7|49|8|@$D|4A|E|4B|J|K]]|9|@]|A|$]]|$1|1E|3|-4|5|6|7|4C|8|@]|9|@]|A|$]]|$1|1F|3|1G|5|6|7|4D|8|@]|9|@]|A|$]]|$1|1H|3|1I|5|6|7|4E|8|@$D|4F|E|4G|J|K]]|9|@]|A|$]]|$1|1J|3|-4|5|6|7|4H|8|@]|9|@]|A|$]]|$1|1K|3|1L|5|6|7|4I|8|@]|9|@]|A|$]]|$1|1M|3|-4|5|6|7|4J|8|@]|9|@]|A|$]]|$1|1N|3|1O|5|I|7|4K|8|@]|9|@]|A|$]]|$1|1P|3|-4|5|6|7|4L|8|@]|9|@]|A|$]]|$1|1Q|3|-4|5|6|7|4M|8|@]|9|@]|A|$]]|$1|1R|3|1S|5|6|7|4N|8|@]|9|@]|A|$]]|$1|1T|3|1U|5|1V|7|4O|8|@$D|4P|E|4Q|J|K]]|9|@]|A|$]]|$1|1W|3|1X|5|1V|7|4R|8|@$D|4S|E|4T|J|K]]|9|@]|A|$]]|$1|1Y|3|-4|5|6|7|4U|8|@]|9|@]|A|$]]|$1|1Z|3|20|5|6|7|4V|8|@$D|4W|E|4X|J|K]]|9|@]|A|$]]|$1|21|3|22|5|1V|7|4Y|8|@$D|4Z|E|50|J|K]]|9|@]|A|$]]|$1|23|3|24|5|6|7|51|8|@]|9|@]|A|$]]|$1|25|3|26|5|1V|7|52|8|@$D|53|E|54|J|K]]|9|@]|A|$]]|$1|27|3|-4|5|6|7|55|8|@]|9|@]|A|$]]|$1|28|3|-4|5|6|7|56|8|@]|9|@]|A|$]]|$1|29|3|-4|5|6|7|57|8|@]|9|@]|A|$]]]|2A|$2B|$5|2C|2D|2E|A|$2F|2G]]|2H|$5|2C|2D|2E|A|$2F|2I]]|2J|$5|2C|2D|2E|A|$2F|2K]]|2L|$5|2C|2D|2E|A|$2F|2M]]|2N|$5|2C|2D|2E|A|$2F|2O]]|2P|$5|2C|2D|2E|A|$2F|2Q]]|2R|$5|2C|2D|2E|A|$2F|2S]]|2T|$5|2C|2D|2E|A|$2F|2S]]|2U|$5|2C|2D|2E|A|$2F|2V]]]]

<h2>Update 2019</h2>

As noted by <a href="https://stackoverflow.com/users/5419381/duct-tape-coder">duct_tape_coder</a> in <a href="https://stackoverflow.com/questions/33190469/linux-machine-with-docker-deploy-windows-container/33190605#comment96408605_33190605">the comments</a>:

<blockquote>
 Microsoft <a href="https://docs.microsoft.com/en-us/virtualization/windowscontainers/container-networking/architecture" rel="noreferrer">has improved the network options for containers</a> and now allows multiple containers per pod with improved namespace.
</blockquote>

<hr>

<h2>In theory (original answer Oct 2015):</h2>

There is no "Windows container" running on a Linux host. 
And a Linux container would not run directly on a Windows server, since <a href="https://stackoverflow.com/a/32757109/6309">it relies on system calls to a Linux kernel</a>.

You certainly can run those Linux containers on any Windows machine through a VM. 
That is what <a href="https://www.docker.com/toolbox" rel="noreferrer">docker toolbox will install</a>.

There will be <a href="https://blog.docker.com/2015/08/tp-docker-engine-windows-server-2016/" rel="noreferrer">support for docker on Windows soon</a>, but that would be for Windows container, not Linux containers.

<a href="https://thenewstack.io/finally-linux-containers-really-will-run-windows-linuxkit/" rel="noreferrer">Update 2017</a>: yes, LinuxKit allows to run a linux container through aa Hyper-V isolation wrapper on a Windows platform, through a minimal Linux OS built from <a href="https://github.com/linuxkit/linuxkit" rel="noreferrer">linuxkit</a>. 
That is still the same idea: linux running inside a VM on Windows. 
That is not a Linux server deployed on a Windows server: only deployed inside a Linux server running in a VM on Windows.

<hr>

<h2>Actually... (update Dec. 2016)</h2>

See "<a href="https://www.mirantis.com/blog/linux-windows-living-together-total-chaos-ok-kubernetes-1-5/" rel="noreferrer">Linux and Windows, living together, total chaos! (OK, Kubernetes 1.5)</a>"

<blockquote>
 Kubernetes 1.5 includes alpha support for both Windows Server Containers, a shared kernel model similar to Docker, and Hyper-V Containers, a single-kernel model that provides better isolation for multi-tenant environments (at the cost of greater latency). 
 The end result is the ability to create a single Kubernetes cluster that includes not just Linux nodes running Linux containers or Windows nodes running Windows containers, but both side by side, for a truly hybrid experience. 
 For example, a single service can have PODs using Windows Server Containers and other PODs using Linux containers.
</blockquote>

But:

<blockquote>
 Though it appears fully functional, there do appear to be some limitations in this early release, including:
 
 <ul>
 <li>The Kubernetes master must still run on Linux due to dependencies in how it’s written. It’s possible to port to Windows, but for the moment the team feels it’s better to focus their efforts on the client components.</li>
 <li>There is no native support for network overlays for containers in windows, so networking is limited to L3. (There are other solutions, but they’re not natively available.) 
 The Kubernetes Windows SIG is working with Microsoft to solve these problems, however, and they hope to have made progress by Kubernetes 1.6’s release early next year.</li>
 <li>Networking between Windows containers is more complicated because each container gets its own network namespace, so it’s recommended that you use single-container pods for now.</li>
 <li>Applications running in Windows Server Containers can run in any language supported by Windows. You CAN run .NET applications in Linux containers, but only if they’re written in .NET Core. .NET core is also supported by the Nano Server operating system, which can be deployed on Windows Server Containers. </li>
 </ul>
</blockquote>

<hr>

I have a Linux server with 16GB ram with docker host installed. I would like to deploy on it a Windows Server container. Is it possible? Anyone has just tried this solution?

Linux machine with docker deploy windows container

Windows Server

Kubernetes

服务器

Windows

容器

Docker

Linux

我有一台Linux服务器，16 ram内存，安装了docker主机。我想在它上面部署一个Windows Server容器。有可能吗？有没有人刚刚试过这个解决方案？

问带有docker部署windows容器的Linux计算机
EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问带有docker部署windows容器的Linux计算机EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问带有docker部署windows容器的Linux计算机
EN