Windows Server containers share the same kernel with the host, as well as each other. Multiple container instances can run concurrently on a host, with isolation provided through namespace, resource control, and process isolation technologies.– This doesn’t mean you can’t test Server 2016 via VirtualBox btw, you just definitely can’t test out Hyper-V containers. The short answer seems to be you can’t, due to a lack of support for Nested Virtualisation despite someone asking for the feature seven years ago. Things were already getting pretty meta in trying to run a Container inside a Virtual Machine on my desktop, but an early challenge I experienced in testing this out was getting the Hyper-V feature to install within a VM running under VirtualBox. That’s a pretty cool move on Microsoft’s part. It’s potentially worth being more explicit here (for anyone not aware) that this isn’t Microsoft’s version of Containers, this is actually Docker baked in to Server 2016.
I’m just starting to get my head around the concept of Containers and as such decided to take Windows Server 2016 Technical Preview 5 for a spin, which includes Docker Containers as a feature.
0 kommentar(er)
