Netherlands: Software

Introductie Windows Server 2016

Issue link:

Contents of this Issue


Page 142 of 173

133 C H A P T E R 6 | App Plat To stop the container, you can use the Stop-Container cmdlet. The container is now up and running, and you obviously would like to manage what is happening within it. You can use the Enter-PSSession cmdlet with a new parameter ContainerName to start a Remote PSSession to the container. Enter-PSSession -ContainerName W2016C1 The session is started then with the container you have running; for example, you can run an IPConfig and validate that you are indeed in the container and running on the right IP address space. Note Container cmdlets and support are continuously increasing as we approach general availability of Windows Server 2016. For updated information and samples about working with containers, go to containers_welcome. What about Docker? Containers are not a new technology. In general, they have existed in the Linux world for quite some time. Docker is an open-source engine that has helped containers become more prevalent. Currently, Docker's open-source runtime builds, ships, and runs containers on Linux operating systems. Because it is open source, an extensive ecosystem of developers, and now "dockerized applications," have grown up around it. Docker provides a user-friendly experience to manage the lifecycle of its containers, facilitating easy adoption. In 2015, Microsoft Azure announced support for the Docker engine on Linux VMs in Azure. This was exciting news, but the question remains: What about Docker on Windows natively? With the introduction of Windows Server containers and Hyper-V containers, Docker becomes even more useful because you can use it to manage Docker containers on Windows as well as the traditional Linux environment. Also, we now have access to all of the images that are available through Docker, so we can download and deploy! The Docker runtime engine will work as an abstraction on top of Windows Server containers and Hyper-V containers. Docker provides all the necessary tooling to develop and operate its engine on top of Windows containers, be it Hyper-V containers or Windows Server containers. This will afford the same flexibility of developing an application in one container and being able to truly run it anywhere. Figure 6-9 shows the placement of the Docker engine in relation to Windows Server containers or Hyper-V containers and compares it to a Docker engine running on Linux. Figure 6-9: The Docker engine on Windows and Linux

Articles in this issue

Links on this page

Archives of this issue

view archives of Netherlands: Software - Introductie Windows Server 2016