Containers for Developers
From a developer’s desktop to a testing machine to a set of production machines, a Docker image can be created that will deploy identically across any environment in seconds. This story has created a massive and growing ecosystem of applications packaged in Docker containers, with DockerHub, the public containerized-application registry that Docker maintains, currently publishing more than 180,000 applications in the public community repository.
When you containerize an app, only the app and the components needed to run the app are combined into an “image”. Containers are then created from this image as you need them. You can also use an image as a baseline to create another image, making image creation even faster. Multiple containers can share the same image, which means containers start very quickly and use fewer resources. For example, you can use containers to spin up light-weight and portable app components – or ‘micro-services’ – for distributed apps and quickly scale each service separately.
Because the container has everything it needs to run your application, they are very portable and can run on any machine that is running Windows Server 2016. You can create and test containers locally, then deploy that same container image to your company’s private cloud, public cloud or service provider. The natural agility of Containers supports modern app development patterns in large scale, virtualized and cloud environments.
With containers, developers can build an app in any language. These apps are completely portable and can run anywhere – laptop, desktop, server, private cloud, public cloud or service provider – without any code changes.
Containers helps developers build and ship higher-quality applications, faster.
- One computer system (physical or virtual) running Windows Server 2016.
- Configure this system with the Windows Container feature and Docker. For a walkthrough on these steps, see Windows Containers on Windows Server.
- QuickStart Windows Containers on Windows 10
- A Docker ID, this will be used to push a container image to Docker Hub. If you do not have a Docker ID, sign up for one at Docker Cloud.
Windows Containers Infrastructure
Microsoft Windows Container with Nano server :
Docker pull microsoft/nanoserver
Docker run -t -I microsoft/nanoserver
Now you are inside the Windows Container on the Nano Server
If you want a Windows Container with Nano Server and IIS running for a website checkout this Docker Pull
More Microsoft images on Docker Hub repositories
Docker run reference
Docker runs processes in isolated containers. A container is a process which runs on a host. The host may be local or remote. When an operator executes
docker run, the container process that runs is isolated in that it has its own file system, its own networking, and its own isolated process tree separate from the host.
Containers can run anywhere !