This is the fourth patch release of the 1.2.z release branch of runc. It
includes a fix for a regression introduced in 1.2.0 related to the
default device list.
- Re-add tun/tap devices to built-in allowed devices lists.
In runc 1.2.0 we removed these devices from the default allow-list
(which were added seemingly by accident early in Docker's history) as
a precaution in order to try to reduce the attack surface of device
inodes available to most containers. At the time we thought
that the vast majority of users using tun/tap would already be
specifying what devices they need (such as by using --device with
Docker/Podman) as opposed to doing the mknod manually, and thus
there would've been no user-visible change.
Unfortunately, it seems that this regressed a noticeable number of
users (and not all higher-level tools provide easy ways to specify
devices to allow) and so this change needed to be reverted. Users
that do not need these devices are recommended to explicitly disable
them by adding deny rules in their container configuration.
full diff: https://github.com/opencontainers/runc/compare/v1.2.3...v1.2.4
release notes: https://github.com/opencontainers/runc/releases/tag/v1.2.4
Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
| ... | ... |
@@ -288,7 +288,7 @@ RUN git init . && git remote add origin "https://github.com/opencontainers/runc. |
| 288 | 288 |
# that is used. If you need to update runc, open a pull request in the containerd |
| 289 | 289 |
# project first, and update both after that is merged. When updating RUNC_VERSION, |
| 290 | 290 |
# consider updating runc in vendor.mod accordingly. |
| 291 |
-ARG RUNC_VERSION=v1.2.3 |
|
| 291 |
+ARG RUNC_VERSION=v1.2.4 |
|
| 292 | 292 |
RUN git fetch -q --depth 1 origin "${RUNC_VERSION}" +refs/tags/*:refs/tags/* && git checkout -q FETCH_HEAD
|
| 293 | 293 |
|
| 294 | 294 |
FROM base AS runc-build |
| ... | ... |
@@ -9,7 +9,7 @@ set -e |
| 9 | 9 |
# the containerd project first, and update both after that is merged. |
| 10 | 10 |
# |
| 11 | 11 |
# When updating RUNC_VERSION, consider updating runc in vendor.mod accordingly |
| 12 |
-: "${RUNC_VERSION:=v1.2.3}"
|
|
| 12 |
+: "${RUNC_VERSION:=v1.2.4}"
|
|
| 13 | 13 |
|
| 14 | 14 |
install_runc() {
|
| 15 | 15 |
RUNC_BUILDTAGS="${RUNC_BUILDTAGS:-"seccomp"}"
|