retrying pr for website to satify cncf guidelines
Signed-off-by: Patrick Chanezon <patlist@chanezon.com> fixing validation issue for whitespace Signed-off-by: Patrick Chanezon <patlist@chanezon.com>
This commit is contained in:
parent
9d155e8164
commit
16f04383ae
@ -4,7 +4,7 @@ The containerd website is built using Jekyll and published to Github pages.
|
|||||||
|
|
||||||
In order to build and test locally:
|
In order to build and test locally:
|
||||||
```
|
```
|
||||||
docker run -v "$PWD":/usr/src/app -p "4000:4000" starefossen/github-pages
|
docker run -it -v "$PWD":/usr/src/app -p "4000:4000" starefossen/github-pages
|
||||||
```
|
```
|
||||||
Then browser to localhost:4000 to see the rendered site. The site autorefreshes when you modify files locally.
|
Then browser to localhost:4000 to see the rendered site. The site autorefreshes when you modify files locally.
|
||||||
|
|
||||||
|
@ -3,7 +3,7 @@
|
|||||||
{% include links.html %}
|
{% include links.html %}
|
||||||
</div>
|
</div>
|
||||||
<div class="copyright">
|
<div class="copyright">
|
||||||
Copyright (c) 2016, Docker Inc.
|
Copyright (c) 2016-2017 the containerd authors
|
||||||
</div>
|
</div>
|
||||||
</div>
|
</div>
|
||||||
<script src="/style/js/jquery-2.1.4.min.js"></script>
|
<script src="/style/js/jquery-2.1.4.min.js"></script>
|
||||||
|
@ -1,3 +1,3 @@
|
|||||||
<div class="link">
|
<div class="link">
|
||||||
<a href="https://github.com/containerd/containerd"><img src="/images/GitHub-Mark-Light-64px.png"/></a>
|
<a href="https://github.com/containerd/containerd"><img src="/images/containerd-light-d.png"/></a>
|
||||||
</div>
|
</div>
|
||||||
|
BIN
docs/images/CNCF_Alternate_Pantone.png
Normal file
BIN
docs/images/CNCF_Alternate_Pantone.png
Normal file
Binary file not shown.
After Width: | Height: | Size: 24 KiB |
@ -20,7 +20,8 @@ containerd includes a daemon exposing gRPC API over a local UNIX socket. The API
|
|||||||
|
|
||||||
containerd is based on the Docker Engine’s core container runtime to benefit from its maturity and existing contributors.
|
containerd is based on the Docker Engine’s core container runtime to benefit from its maturity and existing contributors.
|
||||||
|
|
||||||

|

|
||||||
|
|
||||||
|
|
||||||
## Features and roadmap
|
## Features and roadmap
|
||||||
|
|
||||||
@ -40,7 +41,7 @@ containerd, currently in [version 0.2.4](https://github.com/containerd/container
|
|||||||
|
|
||||||
Containerd [architecture](https://github.com/containerd/containerd/blob/master/design/architecture.md) and [API](https://github.com/containerd/containerd/tree/master/api/) are described in the Github repository.
|
Containerd [architecture](https://github.com/containerd/containerd/blob/master/design/architecture.md) and [API](https://github.com/containerd/containerd/tree/master/api/) are described in the Github repository.
|
||||||
|
|
||||||

|

|
||||||
|
|
||||||
## Principles and Releases
|
## Principles and Releases
|
||||||
|
|
||||||
@ -88,28 +89,35 @@ Each major version will be supported for 1 year with bug fixes and security patc
|
|||||||
|
|
||||||
Docker is a complete platform and programming environment for containerized applications. containerd is one of dozens of specialized components integrated into Docker. Developers and IT professionals looking to build, ship and run containerized applications should continue to use Docker. Operators and integrators looking for specialized components to swap into their platform should consider containerd.
|
Docker is a complete platform and programming environment for containerized applications. containerd is one of dozens of specialized components integrated into Docker. Developers and IT professionals looking to build, ship and run containerized applications should continue to use Docker. Operators and integrators looking for specialized components to swap into their platform should consider containerd.
|
||||||
|
|
||||||

|
|
||||||
|

|
||||||
|
|
||||||
containerd 0.2.4 used in Docker 1.12 covers only container execution and process management.
|
containerd 0.2.4 used in Docker 1.12 covers only container execution and process management.
|
||||||
|
|
||||||

|

|
||||||
|
|
||||||
containerd's roadmap is to refactor the Docker Engine codebase to extract more of its logic for distribution, networking and storage on a single host into a reusable component that Docker will use, and that can be used by other container orchestration projects or hosted container services.
|
containerd's roadmap is to refactor the Docker Engine codebase to extract more of its logic for distribution, networking and storage on a single host into a reusable component that Docker will use, and that can be used by other container orchestration projects or hosted container services.
|
||||||
|
|
||||||

|

|
||||||
|
|
||||||
2. What is the relationship between containerd, OCI and runc?
|
2. What is the relationship between containerd, OCI and runc?
|
||||||
|
|
||||||
Docker [donated the OCI specification to the Linux Foundation in 2015](https://blog.docker.com/2015/06/open-container-project-foundation/), along with a reference implementation called `runc`. containerd integrates [OCI](https://www.opencontainers.org/)/[runc](https://runc.io/) into a feature-complete, production-ready core container runtime. runc is a component of containerd, the executor for containers. containerd has a wider scope than just executing containers: downloading container images, managing storage and network interfaces, calling runc with the right parameters to run containers. containerd fully leverages the Open Container Initiative’s (OCI) runtime, image format specifications and OCI reference implementation (runc) and will pursue OCI certification when it is available. Because of its massive adoption, containerd is the industry standard for implementing OCI.
|
Docker [donated the OCI specification to the Linux Foundation in 2015](https://blog.docker.com/2015/06/open-container-project-foundation/), along with a reference implementation called `runc`. containerd integrates [OCI](https://www.opencontainers.org/)/[runc](https://runc.io/) into a feature-complete, production-ready core container runtime. runc is a component of containerd, the executor for containers. containerd has a wider scope than just executing containers: downloading container images, managing storage and network interfaces, calling runc with the right parameters to run containers. containerd fully leverages the Open Container Initiative’s (OCI) runtime, image format specifications and OCI reference implementation (runc) and will pursue OCI certification when it is available. Because of its massive adoption, containerd is the industry standard for implementing OCI.
|
||||||
|
|
||||||

|

|
||||||
|
|
||||||
3. What is the relationship between containerd and container orchestration systems like Kubernetes and Mesos?
|
3. What is the relationship between containerd and container orchestration systems like Kubernetes and Mesos?
|
||||||
|
|
||||||
Kubernetes today uses Docker directly. In a future version Kubernetes can implement container support in the Kubelet by implementing it's [Container Runtime Interface](https://github.com/kubernetes/kubernetes/blob/release-1.5/docs/devel/container-runtime-interface.md) using containerd. Mesos and other orchestration engines can leverage containerd for core container runtime functionality as well.
|
Kubernetes today uses Docker directly. In a future version Kubernetes can implement container support in the Kubelet by implementing it's [Container Runtime Interface](https://github.com/kubernetes/kubernetes/blob/release-1.5/docs/devel/container-runtime-interface.md) using containerd. Mesos and other orchestration engines can leverage containerd for core container runtime functionality as well.
|
||||||
|
|
||||||

|

|
||||||
|
|
||||||
4. What is the relationship between containerd and cloud managed container services?
|
4. What is the relationship between containerd and cloud managed container services?
|
||||||
|
|
||||||
See answer above: cloud managed container services can leverage containerd instead of Docker in order to provide container functionalities to their users.
|
See answer above: cloud managed container services can leverage containerd instead of Docker in order to provide container functionalities to their users.
|
||||||
|
|
||||||
|
## CNCF
|
||||||
|
|
||||||
|

|
||||||
|
|
||||||
|
We are a Cloud Native Computing Foundation member project.
|
||||||
|
Loading…
Reference in New Issue
Block a user