Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update module github.com/opencontainers/runc to v1.2.2 #5840

Merged

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Nov 16, 2024

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
github.com/opencontainers/runc v1.2.1 -> v1.2.2 age adoption passing confidence

Release Notes

opencontainers/runc (github.com/opencontainers/runc)

v1.2.2: runc v1.2.2 -- "Specialization is for insects."

Compare Source

This is the second patch release of the 1.2.z branch of runc. It
includes two fixes for problems introduced in runc 1.2.0, as well as
some documentation improvements surrounding the overlayfs /proc/self/exe
protections.

  • Fixed the failure of runc delete on a rootless container with no
    dedicated cgroup on a system with read-only /sys/fs/cgroup mount.
    This is a regression in runc 1.2.0, causing a failure when using
    rootless buildkit. (#​4518, #​4531)
  • Using runc on a system where /run/runc and /usr/bin are on different
    filesystems no longer results in harmless but annoying messages
    ("overlayfs: "xino" feature enabled using 3 upper inode bits")
    appearing in the kernel log. (#​4508, #​4530)
  • Better memfd-bind documentation. (#​4530)
  • CI: bump Fedora 40 -> 41. (#​4528)
Static Linking Notices

The runc binary distributed with this release are statically linked with
the following GNU LGPL-2.1 licensed libraries, with runc acting
as a "work that uses the Library":

The versions of these libraries were not modified from their upstream versions,
but in order to comply with the LGPL-2.1 (§6(a)), we have attached the
complete source code for those libraries which (when combined with the attached
runc source code) may be used to exercise your rights under the LGPL-2.1.

However we strongly suggest that you make use of your distribution's packages
or download them from the authoritative upstream sources, especially since
these libraries are related to the security of your containers.


Thanks to all of the contributors who made this release possible:

Signed-off-by: Aleksa Sarai [email protected]


Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Never, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

Signed-off-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
@renovate renovate bot added the dependencies Pull requests that update a dependency file label Nov 16, 2024
@nalind
Copy link
Member

nalind commented Nov 19, 2024

/approve
/lgtm

Copy link
Contributor

openshift-ci bot commented Nov 19, 2024

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: nalind, renovate[bot]

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-merge-bot openshift-merge-bot bot merged commit 52437ef into main Nov 19, 2024
32 checks passed
@renovate renovate bot deleted the renovate/github.com-opencontainers-runc-1.x branch November 19, 2024 21:32
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved dependencies Pull requests that update a dependency file lgtm
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant