You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For other architectures and distribution support, you will find that many
238
237
Linux distributions package their own containerd and provide it across several
@@ -262,7 +261,7 @@ loaded for the user's shell environment.
262
261
263
262
`cri` is a [containerd](https://containerd.io/) plugin implementation of the Kubernetes [container runtime interface (CRI)](https://github.com/kubernetes/cri-api/blob/master/pkg/apis/runtime/v1alpha2/api.proto). With it, you are able to use containerd as the container runtime for a Kubernetes cluster.
264
263
265
-

264
+

266
265
267
266
#### CRI Status
268
267
@@ -286,7 +285,7 @@ A Kubernetes incubator project, [cri-tools](https://github.com/kubernetes-sigs/c
286
285
#### CRI Guides
287
286
*[Bringing up a Production Quality Cluster on GCE](docs/cri/kube-up.md)
288
287
*[Installing with Ansible and Kubeadm](contrib/ansible/README.md)
289
-
*[For Non-Ansible Users, Preforming a Custom Installation Using the Release Tarball and Kubeadm](docs/installation.md)
288
+
*[For Non-Ansible Users, Preforming a Custom Installation Using the Release Tarball and Kubeadm](docs/cri/installation.md)
Copy file name to clipboardExpand all lines: docs/cri/installation.md
+68-44Lines changed: 68 additions & 44 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,50 +4,74 @@ This document provides the steps to install `containerd` and its dependencies wi
4
4
These steps have been verified on Ubuntu 16.04. For other OS distributions, the steps may differ. Please feel free to file issues or PRs if you encounter any problems on other OS distributions.
5
5
6
6
*Note: You need to run the following steps on each node you are planning to use in your Kubernetes cluster.*
7
+
7
8
## Release Tarball
8
-
For each `containerd` release, we'll publish a release tarball specifically for Kubernetes named `cri-containerd-${VERSION}.${OS}-${ARCH}.tar.gz`. This release tarball contains all required binaries and files for using `containerd` with Kubernetes. For example, the 1.2.4 version is available at https://storage.googleapis.com/cri-containerd-release/cri-containerd-1.2.4.linux-amd64.tar.gz.
9
+
For each `containerd` release, we'll publish a release tarball specifically for Kubernetes named `cri-containerd-cni-${VERSION}-${OS}-${ARCH}.tar.gz`. This release tarball contains all required binaries and files for using `containerd` with Kubernetes. For example, the 1.4.3 version is available at https://github.com/containerd/containerd/releases/download/v1.4.3/cri-containerd-cni-1.4.3-linux-amd64.tar.gz.
9
10
10
-
Note: The VERSION tag specified for the tarball corresponds to the `containerd` release tag, not a containerd/cri repository release tag. The `containerd` release includes the containerd/cri repository code through vendoring. The containerd/cri version of the containerd/cri code included in `containerd` is specified via a commit hash for containerd/cri in containerd/containerd/vendor.conf.
11
11
### Content
12
12
As shown below, the release tarball contains:
13
-
1)`containerd`, `containerd-shim`, `containerd-stress`, `containerd-release`, `ctr`: binaries for containerd.
14
-
2)`runc`: runc binary.
15
-
3)`crictl`, `crictl.yaml`: command line tools for CRI container runtime and its config file.
16
-
4)`critest`: binary to run [CRI validation test](https://github.com/kubernetes-sigs/cri-tools/blob/master/docs/validation.md).
17
-
5)`containerd.service`: Systemd unit for containerd.
18
-
6)`/opt/containerd/cluster/`: scripts for `kube-up.sh`.
13
+
14
+
-`containerd`, `containerd-shim`, `containerd-shim-runc-v1`, `containerd-shim-runc-v2`, `ctr`: binaries for containerd.
15
+
-`runc`: runc binary.
16
+
-`/opt/cni/bin`: binaries for [Container Network Interface](https://github.com/containernetworking/cni)
17
+
-`crictl`, `crictl.yaml`: command line tools for CRI container runtime and its config file.
18
+
-`critest`: binary to run [CRI validation test](https://github.com/kubernetes-sigs/cri-tools/blob/master/docs/validation.md).
19
+
-`containerd.service`: Systemd unit for containerd.
20
+
-`/opt/containerd/cluster/`: scripts for `kube-up.sh`.
21
+
19
22
```console
20
-
$ tar -tf cri-containerd-1.1.0-rc.0.linux-amd64.tar.gz
If you are using systemd, just simply unpack the tarball to the root directory:
88
111
```bash
89
-
sudo tar --no-overwrite-dir -C / -xzf cri-containerd-${VERSION}.linux-amd64.tar.gz
112
+
sudo tar --no-overwrite-dir -C / -xzf cri-containerd-cni-${VERSION}-linux-amd64.tar.gz
113
+
sudo systemctl daemon-reload
90
114
sudo systemctl start containerd
91
115
```
92
116
If you are not using systemd, please unpack all binaries into a directory in your `PATH`, and start `containerd` as monitored long running services with the service manager you are using e.g. `supervisord`, `upstart` etc.
0 commit comments