Skip to content

[release/1.6] update runc binary to v1.1.3#7036

Merged
mikebrow merged 1 commit intocontainerd:release/1.6from
thaJeztah:1.6_update_runc2
Jun 9, 2022
Merged

[release/1.6] update runc binary to v1.1.3#7036
mikebrow merged 1 commit intocontainerd:release/1.6from
thaJeztah:1.6_update_runc2

Conversation

@thaJeztah
Copy link
Member

full diff: opencontainers/runc@v1.1.2...v1.1.3

This is the third release of the 1.1.z series of runc, and contains
various minor improvements and bugfixes.

  • Our seccomp -ENOSYS stub now correctly handles multiplexed syscalls on
    s390 and s390x. This solves the issue where syscalls the host kernel did not
    support would return -EPERM despite the existence of the -ENOSYS stub
    code (this was due to how s390x does syscall multiplexing).
  • Retry on dbus disconnect logic in libcontainer/cgroups/systemd now works as
    intended; this fix does not affect runc binary itself but is important for
    libcontainer users such as Kubernetes.
  • Inability to compile with recent clang due to an issue with duplicate
    constants in libseccomp-golang.
  • When using systemd cgroup driver, skip adding device paths that don't exist,
    to stop systemd from emitting warnings about those paths.
  • Socket activation was failing when more than 3 sockets were used.
  • Various CI fixes.
  • Allow to bind mount /proc/sys/kernel/ns_last_pid to inside container.
  • runc static binaries are now linked against libseccomp v2.5.4.

(cherry picked from commit 0167e55)

full diff: opencontainers/runc@v1.1.2...v1.1.3

This is the third release of the 1.1.z series of runc, and contains
various minor improvements and bugfixes.

- Our seccomp `-ENOSYS` stub now correctly handles multiplexed syscalls on
  s390 and s390x. This solves the issue where syscalls the host kernel did not
  support would return `-EPERM` despite the existence of the `-ENOSYS` stub
  code (this was due to how s390x does syscall multiplexing).
- Retry on dbus disconnect logic in libcontainer/cgroups/systemd now works as
  intended; this fix does not affect runc binary itself but is important for
  libcontainer users such as Kubernetes.
- Inability to compile with recent clang due to an issue with duplicate
  constants in libseccomp-golang.
- When using systemd cgroup driver, skip adding device paths that don't exist,
  to stop systemd from emitting warnings about those paths.
- Socket activation was failing when more than 3 sockets were used.
- Various CI fixes.
- Allow to bind mount `/proc/sys/kernel/ns_last_pid` to inside container.
- runc static binaries are now linked against libseccomp v2.5.4.

Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
(cherry picked from commit 0167e55)
Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
Copy link
Member

@mikebrow mikebrow left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@mikebrow mikebrow merged commit 9abd4b3 into containerd:release/1.6 Jun 9, 2022
@thaJeztah thaJeztah deleted the 1.6_update_runc2 branch June 10, 2022 06:32
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants