Microsoft Partners With Docker
rjmarvin writes Docker is teaming up with Microsoft to bring its open container technology to the next release of Windows Server. Docker Engine will work with the next release of Windows Server and images will be available in Docker Hub, which will also integrate directly into Microsoft Azure. The partnership moves Docker beyond Linux for the first time with new multi-container application capabilities for cloud and enterprise developers.
Docker isn't niche. It is one of the core technologies for DevOps which is designing application infrastructures where IT provides a platform for in-house and integrate micro-services rather than providing monolithic applications to departments. Many PaaS systems are based on Docker particularly Helion (HP), CenturyLink, Rackspace its a big player for AWS...
Of the terms you threw out, I know what IT is, and I've "heard" of Rackspace -- but only because of adverspam; I have no idea what they do.
DevOps = never heard of it
PaaS = no freaking clue
Helion = no earthly idea (and why area you referencing Hewlett-Packard?)
CenturyLink = I got nothing
AWS = nada
Ok here is the bloated form for people like you who can't seem to operate a search engine and need every term explained to them or directly linked.
Docker (which is an open platform for developers and sysadmins to build, ship, and run distributed applications. Consisting of Docker Engine, a portable, lightweight runtime and packaging tool, and Docker Hub, a cloud service for sharing applications and automating workflows, Docker enables apps to be quickly assembled from components and eliminates the friction between development, QA, and production environments. As a result, IT can ship faster and run the same app, unchanged, on laptops, data center VMs, and any cloud) isn't niche. It is one of the core technologies for DevOps (a concept dealing with, among other things: software development, operations, and services. It emphasizes communication, collaboration, and integration between software developers and information technology (IT) operations personnel) which is designing application infrastructures where IT provides a platform for in-house and integrate micro-services (that are small, independent processes communicating with each other using language-agnostic APIs to form complex applications) rather than providing monolithic applications (single-tiered software applications in which the user interface and data access code are combined into a single program from a single platform) to departments. Many PaaS (Platform as a Service, a category of cloud computing services that provides a computing platform and a solution stack as a service) systems are based on Docker particularly Helion, CenturyLink, Rackspace its a big player for AWS...
So much easier to understand right?
Docker is sort of an extremely lightweight virtual machines system.
Docker organizes software into "containers". Each container has a complete set of libraries and files, and each container is isolated from the rest of the system. Thus if you need a specific and touchy set of libraries to run Software X, and you need a different specific and touchy set of libraries to run Software Y, you can simply make two containers and run them side by side.
As I understand it, Docker container images use a "snapshots" system to store changes; so the two containers for Software X and Software Y will together be much smaller than two VM images would be.
Using Docker, if developers make a server-side application, they can then hand a container over to production for deployment, and everyone can be confident that the application will run the same in production as it ran in development. (Of course it would still be possible to break things, for example by having different data in the production database compared to the dev test database.) Or, developers could run containers on their laptops and expect them to run the same as on the servers in the office.
Unlike VMs, the Docker containers don't run their own kernels. So you can't run a Linux server with Docker that in turn runs OpenBSD in a container.
As I understand it, many people use Docker to run a single process per container. The web server in one container, the email server in another, the SSH server in another, etc. One use case: if you have a web site hosted in the cloud, and the Slashdot effect starts slamming on the web site, the cloud hosting service could spin up another 500 instances of the web site (500 fresh instances of the Docker container, each container running a single process, the web server).
I talked to an expert sysadmin, and he told me "This is the future." I'm going to set up a Docker server at home and learn my way around it.
https://www.docker.com/whatisdocker/
My reading of the press release is that Microsoft is going to (a) implement the Docker APIs for Windows, so that Windows server applications can be container-ized; and (b) add the ability to run Linux containers. The latter is not implausible; Windows NT has always had so-called "personalities" and Posix has been available as a personality for decades.
http://en.wikipedia.org/wiki/Hybrid_kernel#NT_kernel
lf(1): it's like ls(1) but sorts filenames by extension, tersely