Docker: Difference between revisions
Jump to navigation
Jump to search
| Line 15: | Line 15: | ||
Open Container Initiative | Open Container Initiative | ||
* [https://www.opencontainers.org Open Container Initiative (OCI)] | * [https://www.opencontainers.org Open Container Initiative (OCI)] | ||
* | * [https://github.com/opencontainers/runtime-spec OCI runtime specification]. | ||
* Google [https://github.com/opencontainers/runc code for running containers as a tool and library called runc] | |||
When you run a Docker container, these are the steps Docker actually goes through: | When you run a Docker container, these are the steps Docker actually goes through: | ||
Revision as of 19:45, 13 November 2020
Full Title or Meme
Docker is a system for building, deploying and running complex images of a program with its runtime.
Context
- With the rise of cloud computing the need arose to give users an easy way to create a run-time package that could be sent to any cloud Platform as a Service provider (PaaS) with complete interoperability.
Solutions
Docker was released in 2013 and solved many of the problems that developers had running containers end-to-end. It had all these things:
- A container image format
- A method for building container images (Dockerfile/docker build)
- A way to manage container images (docker images, docker rm , etc.)
- A way to manage instances of containers (docker ps, docker rm , etc.)
- A way to share container images (docker push/pull)
- A way to run containers (docker run)
Open Container Initiative
- Open Container Initiative (OCI)
- OCI runtime specification.
- Google code for running containers as a tool and library called runc
When you run a Docker container, these are the steps Docker actually goes through:
- Download the image
- Unpack the image into a "bundle". This flattens the layers into a single filesystem.
- Run the container from the bundle