How does docker compare to openshift?

Question

Docker and OpenShift are both frameworks to implement a PaaS service.

How do they compare in architecture and features?

Answer 1

I thought I should update the answers to this question with information available near the end of 2018.

The situation right now is a little more complicated than when the question was originally asked. Right now Docker Inc. is the primary developer of docker and Moby -- which is currently the upstream project for the docker runtime and the commercial enterprise edition of docker, imaginatively called Docker Enterprise Edition.

Contemporary analysis of this question would result in a comparison of Docker Enterprise Edition with RedHat OpenShift. These container platforms are in direct competition with each other and both are considered to be Kubernetes distributions that can be run on-prem and in the cloud. At the time of writing, Docker Inc.'s Docker-EE is leading the pack in terms of features and sales, but there is stiff competition from the public-cloud providers who are offering kubernetes Platform(s) as a Service and are starting to move into more advanced Serverless Container Platforms.

Answer 2

The primary difference is that Docker as a project is focused on the runtime container only, whereas OpenShift (as a system) includes both the runtime container as well as the REST API, coordination, and web interfaces to deploy and manage individual containers.

Comparing just the runtime containers, OpenShift and Docker both use kernel isolation features to keep tenant processes separate. For Docker that is primarily through LXC and for OpenShift that is largely through SELinux and Multiple Category Security (MCS). Both use cgroups to limit the CPU, memory, and IO of tenants. Upstream OpenShift is looking at LXC to reduce long term effort.

Docker uses AUFS for advanced disk and file copy-on-write sharing, OpenShift neither requires nor is incompatible with such a system.

Inside the container, OpenShift models units of functionality (web servers, dbs) via "cartridges", which are a set of shell script hooks that are called when the system is invoked. The API is described here. A cartridge is roughly similar to a docker image.

Openshift also describes the API by which a broker (coordinator) communicates with nodes (servers that host multiple tenant containers) to invoke endpoints in that container.

EDITED TO ADD: As of June 2015, OpenShift Origin 1.0 runs on top of Docker and Kubernetes, and you can build and develop multi container apps that run on the Docker runtime. OpenShift adds build, image workflow and promotion, and secure container cluster operations on top of Kube and Docker

Answer 3

Here is by the far the best beginner explanation. https://deis.com/blog/2016/kubernetes-illustrated-guide/

This isn't a joke, sometimes we need to view things as a child would in order to really understand.

I would not say they are even comparable. Openshift is an enterprise solution by redhat that builds on kubernetes. Kubernetes is just a framework to help organize and automate working with docker containers. I would start with the video and then look at kupernetes at a lower level. Once you are comfortable then start looking into the the features that openshift adds.

Answer 4

I have found some interesting readings about this topic over the past two years:

• Openshift is a PaaS architecture that makes use of docker container technology.
• That happened just not soon ago when openshift changed from gears to docker pods.
• The technology fits into the bigger cloud stack architecture in general at the layer 3, the PaaS layer. The other layers in the model: 0 - hardware; 1 - software-defined data center; 2 - foundational PaaS; 4 - model-driven PaaS; 5 - app service; 6 - SaaS.