-1

Let's say I have Windows Server 2016 Desktop where I will deploy my micro services as containers. Also, let's say I choose Windows Server Core as base image for my containers. This force me to choose Hyper-v containers.

Is it even resonable to run Windows Server Core as base image in a hyper-v container? I mean, Windows Server Core is quite big in terms of disk space memory (at least compared to Nano Server).

What are the main differences between having Windows Server Core and Windows Server Nano as base image in a hyper-v container? I'm thinking about RAM usage, disk space usage in the host. Ex, If I have many containers (10-20), will that be a problem if using Server Core (because of its larger size)?

4

1 回答 1

2

我知道使用安装了 hyper-v 的 Windows 10 Pro 尝试过这个：

以 Windows Server Nano 作为基础映像的 Hyper-v 容器。容器启动时间是几秒钟。进程内存（vmmem 进程）约 200Mb。

以 Windows Server Core（安装了 IIS）作为基础镜像的 Hyper-v 容器。容器启动时间约为 30 秒。进程内存（vmmem进程）约400Mb

改天我将使用常规容器而不是 hyper-v 容器进行相同的测试。为此，我需要在 Assure 中使用 Desktop UI 启动 Windows Server 2016。

编辑：我现在已经测试了常规容器。启动时间大约是 hyper-v 容器的一半。由于容器与主机共享内核，内存使用几乎为零。

于 2016-10-29T21:00:50.560 回答