move runc version to a separate file for easier consumption
This moves the runc version to build to scripts/setup/runc-version, which makes it easier for packagers to find the default version to use. The RUNC_VERSION environment variable can still be used to override the version, which can be used (e.g.) to test against different versions in our CI. Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
This commit is contained in:
@@ -3,13 +3,13 @@ provided by [runc](https://github.com/opencontainers/runc).
|
||||
|
||||
Development (`-dev`) and pre-releases of containerd may depend features in `runc`
|
||||
that have not yet been released, and may require a specific runc build. The version
|
||||
of runc that is tested against in our CI can be found in the `RUNC_VERSION` variable
|
||||
in the [`script/setup/install-runc`](../script/setup/install-runc) script, which
|
||||
may point to a git-commit (for pre releases) or tag in the runc repository.
|
||||
of runc that is tested against in our CI can be found in the [`script/setup/runc-version`](../script/setup/runc-version)
|
||||
file, which may point to a git-commit (for pre releases) or tag in the runc
|
||||
repository.
|
||||
|
||||
For regular (non-pre-)releases of containerd releases, we attempt to use released
|
||||
(tagged) versions of runc. We recommend using a version of runc that's equal to
|
||||
or higher than the version of runc described in [`script/setup/install-runc`](../script/setup/install-runc).
|
||||
or higher than the version of runc described in [`script/setup/runc-version`](../script/setup/runc-version).
|
||||
|
||||
If you encounter any runtime errors, make sure your runc is in sync with the
|
||||
commit or tag provided in that file.
|
||||
|
||||
Reference in New Issue
Block a user