The website uses cookies. By using this site, you agree to our use of cookies as described in the Privacy Policy.
I Agree
Text direction?

containerd/ at master · containerd/containerd


Join GitHub today

GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.

Sign up
Actually we have been testing containerd with the runc version that is defined
in vendor.conf rather than the one defined in (`script/setup/install-runc`).

This commit makes sure that the revision defined in vendor.conf is always the desired one.

Signed-off-by: Akihiro Suda <>
4 contributors
25 lines (15 sloc) 1.27 KB

containerd is built with OCI support and with support for advanced features provided by runc.

We depend on a specific runc version when dealing with advanced features. You should have a specific runc build for development. The current supported runc commit is described in vendor.conf. Please refer to the line that starts with

For more information on how to clone and build runc see the runc Building documentation.

Note: before building you may need to install additional support, which will vary by platform. For example, you may need to install libseccomp e.g. libseccomp-dev for Ubuntu.


From within your opencontainers/runc repository run:


make BUILDTAGS='seccomp apparmor' && sudo make install


make BUILDTAGS='seccomp selinux' && sudo make install

After an official runc release we will start pinning containerd support to a specific version but various development and testing features may require a newer runc version than the latest release. If you encounter any runtime errors, please make sure your runc is in sync with the commit/tag provided in this document.

Related Notes
Get a free MyMarkup account to save this article and view it later on any device.
Create account

End User License Agreement

Summary | 1 Annotation
specific runc version when dealing with advanced features
2020/07/27 09:49