Return Markdown files to /docs directory
Signed-off-by: Luc Perkins <lucperkins@gmail.com>
This commit is contained in:
parent
dc2e115f8b
commit
e5e63539a6
@ -1,7 +1,4 @@
|
|||||||
---
|
# Client options
|
||||||
title: Client options
|
|
||||||
draft: true
|
|
||||||
---
|
|
||||||
|
|
||||||
The containerd client was built to be easily extended by consumers.
|
The containerd client was built to be easily extended by consumers.
|
||||||
The goal is that the execution flow of the calls remain the same across implementations while `Opts` are written to extend functionality.
|
The goal is that the execution flow of the calls remain the same across implementations while `Opts` are written to extend functionality.
|
@ -1,8 +1,3 @@
|
|||||||
---
|
|
||||||
title: Dockercon 2017 Summit
|
|
||||||
draft: true
|
|
||||||
---
|
|
||||||
|
|
||||||
# Dockercon 2017 Summit
|
# Dockercon 2017 Summit
|
||||||
|
|
||||||
This year at Dockercon US 2017 we will be having a containerd Summit on Thursday morning the week of the conference.
|
This year at Dockercon US 2017 we will be having a containerd Summit on Thursday morning the week of the conference.
|
@ -1,7 +1,4 @@
|
|||||||
---
|
# Getting started with containerd
|
||||||
title: Getting started with containerd
|
|
||||||
draft: true
|
|
||||||
---
|
|
||||||
|
|
||||||
There are many different ways to use containerd.
|
There are many different ways to use containerd.
|
||||||
If you are a developer working on containerd you can use the `ctr` tool to quickly test features and functionality without writing extra code.
|
If you are a developer working on containerd you can use the `ctr` tool to quickly test features and functionality without writing extra code.
|
@ -1,7 +1,4 @@
|
|||||||
---
|
# containerd Namespaces and Multi-Tenancy
|
||||||
title: containerd Namespaces and Multi-Tenancy
|
|
||||||
draft: true
|
|
||||||
---
|
|
||||||
|
|
||||||
containerd offers a fully namespaced API so multiple consumers can all use a single containerd instance without conflicting with one another.
|
containerd offers a fully namespaced API so multiple consumers can all use a single containerd instance without conflicting with one another.
|
||||||
Namespaces allow multi-tenancy within a single daemon. This removes the need for the common pattern of using nested containers to achieve this separation.
|
Namespaces allow multi-tenancy within a single daemon. This removes the need for the common pattern of using nested containers to achieve this separation.
|
@ -1,7 +1,4 @@
|
|||||||
---
|
# containerd for Ops and Admins
|
||||||
title: containerd for Ops and Admins
|
|
||||||
draft: true
|
|
||||||
---
|
|
||||||
|
|
||||||
containerd is meant to be a simple daemon to run on any system.
|
containerd is meant to be a simple daemon to run on any system.
|
||||||
It provides a minimal config with knobs to configure the daemon and what plugins are used when necessary.
|
It provides a minimal config with knobs to configure the daemon and what plugins are used when necessary.
|
Loading…
Reference in New Issue
Block a user