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 proper results, install the `protoc` release into `/usr/local` on your build system. For example, the following commands will download and install the 3.11.4 release for a 64-bit Linux host:
Make sure to follow the guidelines for versioning in [RUNC.md](RUNC.md) for the
77
-
best results. Some pointers on proper build tag setupVersion mismatches can
78
-
result in undefined behavior.
73
+
best results.
79
74
80
75
## Build containerd
81
76
82
77
`containerd` uses `make` to create a repeatable build flow. It means that you
83
78
can run:
84
79
85
80
```
86
-
cd $GOPATH/src/github.com/containerd/containerd
81
+
cd containerd
87
82
make
88
83
```
89
84
@@ -111,7 +106,10 @@ make generate
111
106
> For example, adding `BUILDTAGS=no_btrfs` to your environment before calling the **binaries**
112
107
> Makefile target will disable the btrfs driver within the containerd Go build.
113
108
114
-
Vendoring of external imports uses the [`vndr` tool](https://github.com/LK4D4/vndr) which uses a simple config file, `vendor.conf`, to provide the URL and version or hash details for each vendored import. After modifying `vendor.conf` run the `vndr` tool to update the `vendor/` directory contents. Combining the `vendor.conf` update with the changeset in `vendor/` after running `vndr` should become a single commit for a PR which relies on vendored updates.
109
+
Vendoring of external imports uses the [Go Modules](https://golang.org/ref/mod#vendoring). You need
110
+
to use `go mod` command to modify the dependencies. After modifition, you should run `go mod tidy`
111
+
and `go mod vendor` to ensure the `go.mod`, `go.sum` files and `vendor` directory are up to date.
112
+
Changes to these files should become a single commit for a PR which relies on vendored updates.
115
113
116
114
Please refer to [RUNC.md](/RUNC.md) for the currently supported version of `runc` that is used by containerd.
117
115
@@ -131,6 +129,8 @@ make EXTRA_FLAGS="-buildmode pie" \
131
129
132
130
# Via Docker container
133
131
132
+
The following instructions assume you are at the parent directory of containerd source directory.
133
+
134
134
## Build containerd
135
135
136
136
You can build `containerd` via a Linux-based Docker container.
@@ -148,7 +148,7 @@ containerd source root directory you can run the following command:
@@ -249,6 +248,16 @@ the autocomplete/ctr file in your `.bashrc`, or manually like:
249
248
$ source ./contrib/autocomplete/ctr
250
249
```
251
250
251
+
#### Distribution of `ctr` autocomplete for bash and zsh
252
+
253
+
For bash, copy the `contrib/autocomplete/ctr` script into
254
+
`/etc/bash_completion.d/` and rename it to `ctr`. The `zsh_autocomplete`
255
+
file is also available and can be used similarly for zsh users.
256
+
257
+
Provide documentation to users to `source` this file into their shell if
258
+
you don't place the autocomplete file in a location where it is automatically
259
+
loaded for the user's shell environment.
260
+
252
261
### CRI
253
262
254
263
`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.
@@ -283,16 +292,6 @@ A Kubernetes incubator project, [cri-tools](https://github.com/kubernetes-sigs/c
0 commit comments