chore(deps): update dependency containers/podman to v5.2.0

[uniget-bot]

This PR contains the following updates:

Package	Update	Change
containers/podman	minor	5.1.2 -> 5.2.0

---

Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.

---

Release Notes

containers/podman (containers/podman)

v5.2.0

Compare Source

Features

• Podman now supports libkrun as a backend for creating virtual machines on MacOS. The libkrun backend has the advantage of allowing GPUs to be mounted into the virtual machine to accelerate tasks. The default backend remains applehv.
• Quadlet now has support for .build files, which allows images to be built by Quadlet and then used by Quadlet containers.
• Quadlet .container files now support two new fields, LogOpt to specify container logging configuration and StopSignal to specify container stop signal (#​23050).
• Quadlet .container and .pod files now support a new field, NetworkAlias, to add network aliases.
• Quadlet drop-in search paths have been expanded to include top-level type drop-ins (container.d, pod.d) and truncated unit drop-ins (unit-.container.d) (#​23158).
• Podman now supports a new command, podman system check, which will identify (and, if possible, correct) corruption within local container storage.
• The podman machine reset command will now reset all providers available on the current operating system (e.g. ensuring that both HyperV and WSL podman machine VMs will be removed on Windows).

Changes

• Podman now requires the new kernel mount API, introducing a dependency on Linux Kernel v5.2 or higher.
• Quadlet .image units now have a dependency on network-online.target (#​21873).
• The --device option to podman create and podman run is no longer ignored when --privileged is also specified (#​23132).
• The podman start and podman stop commands no longer print the full ID of the pod started/stopped, but instead the user's input used to specify the pod (e.g. podman pod start b will print b instead of the pod's full ID) (#​22590).
• Virtual machines created by podman machine on Linux now use virtiofs instead of 9p for mounting host filesystems. Existing mounts will be transparently changed on machine restart or recreation. This should improve performance and reliability of host mounts. This requires the installation of virtiofsd on the host system to function.
• Using both the --squash and --layers=false options to podman build at the same time is now allowed.
• Podman now passes container's stop timeout to systemd when creating cgroups, causing it to be honored when systemd stops the scope. This should prevent hangs on system shutdown due to running Podman containers.
• The --volume-driver option to podman machine init is now deprecated.

Bugfixes

• Fixed a bug where rootless containers created with the --sdnotify=healthy option could panic when started (#​22651).
• Fixed a bug where containers created with the --sdnotify=healthy option that exited quickly would sometimes return an error instead of notifying that the container was ready (#​22760).
• Fixed a bug where the podman system reset command did not remove the containers/image blob cache (#​22825).
• Fixed a bug where Podman would sometimes create a cgroup for itself even when the --cgroups=disabled option was specified at container creation time (#​20910).
• Fixed a bug where the /etc/hosts file in a container was not created with a newline at the end of the file (#​22729).
• Fixed a bug where the podman start command could sometimes panic when starting a container in the stopped state.
• Fixed a bug where the podman system renumber command would fail if volumes existed when using the sqlite database backend (#​23052).
• Fixed a bug where the podman container restore command could not successfully restore a container in a pod.
• Fixed a bug where an error message from podman diff would suggest using the --latest option when using the remote Podman client (#​23038).
• Fixed a bug where user could assign more memory to a Podman machine than existed on the host (#​18206).
• Fixed a bug where the podman events command was rarely unable to report errors that occurred (#​23165).
• Fixed a bug where containers run in systemd units would sometimes not be removed correctly on exit when using the --cidfile option.
• Fixed a bug where the first Podman command run after a reboot could cause hang when using transient mode (#​22984).
• Fixed a bug where Podman could throw errors about a database configuration mismatch if certain paths did not exist on the host.
• Fixed a bug where the podman run and podman start commands could throw strange errors if another Podman process stopped the container at a midpoint in the process of starting (#​23246).
• Fixed a bug where the podman system service command could leak a mount on termination.
• Fixed a bug where the Podman remote client would panic if an invalid image filter was passed to podman images (#​23120).
• Fixed a bug where the podman auto-update and podman system df commands could fail when a container was removed while the command was running (#​23279).
• Fixed a bug where the podman machine init command could panic when trying to decompress an empty file when preparing the VM image (#​23281).
• Fixed a bug where the podman ps --pod and podman pod stats commands could sometimes fail when a pod was removed while the command was running (#​23282).
• Fixed a bug where the podman stats and podman pod stats commands would sometimes exit with a container is stopped error when showing all containers (or pod containers, for pod stats) if a container stopped while the command was running (#​23334).
• Fixed a bug where the output of container healthchecks was not properly logged if it did not include a final newline (#​23332).
• Fixed a bug where the port forwarding firewall rules of an existing container could be be overwritten when starting a second container which forwarded the same port on the host even if the second container failed to start as the port was already bound.
• Fixed a bug where the containers created by the podman play kube command could sometimes not properly clean up their network stacks (#​21569).

API

• The Build API for Images now accepts a comma-separated list in the Platform query parameter, allowing a single API call to built an image for multiple architectures (#​22071).
• Fixed a bug where the Remove endpoint for Volumes would return an incorrectly formatted error when called with an ambiguous volume name (#​22616).
• Fixed a bug where the Stats endpoint for Containers would return an incorrectly formatted error when called on a container that did not exist (#​22612).
• Fixed a bug where the Start endpoint for Pods would return a 409 error code in cases where a 500 error code should have been returned (#​22989).
• Fixed a bug where the Top endpoint for Pods would return a 200 status code and then subsequently an error (#​22986).

Misc

• Podman no longer requires all parent directories of its root and runroot to be world-executable (#​23028).
• Error messages from the podman build command when the -f option is given, but points to a file that does not exist, have been improved (#​22940).
• The Podman windows installer is now built using WiX 5.
• Updated the gvisor-tap-vsock library to v0.7.4. This release contains a fix for a gvproxy crash on macOS when there is heavy network traffic on a fast link.
• Updated Buildah to v1.37.0
• Updated the containers/image library to v5.32.0
• Updated the containers/storage library to v1.55.0
• Updated the containers/common library to v0.60.0

---

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: Whenever PR becomes conflicted, 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 has been generated by Renovate Bot.

[nicholasdille-bot]

Auto-approved because label type/renovate is present.

[github-actions]

🔍 Vulnerabilities of ghcr.io/uniget-org/tools/podman:5.2.0

📦 Image Reference ghcr.io/uniget-org/tools/podman:5.2.0

digest	sha256:8d4314281281e595ed23c370b10883bf450bebea48ab2eb2d621c5bdff65ca3e
vulnerabilities
platform	linux/amd64
size	33 MB
packages	172

github.com/opencontainers/runc 1.1.1-0.20240131200429-02120488a4c0 (golang) pkg:golang/github.com/opencontainers/runc@1.1.1-0.20240131200429-02120488a4c0 OWASP Top Ten 2017 Category A9 - Using Components with Known Vulnerabilities Affected range <1.2.0-rc.1 Fixed version 1.2.0-rc.1 CVSS Score 7.2 CVSS Vector CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H Description Withdrawn Advisory This advisory has been withdrawn because it was incorrectly attributed to runc. Please see the issue here for more information. Original Description A flaw was found in cri-o, where an arbitrary systemd property can be injected via a Pod annotation. Any user who can create a pod with an arbitrary annotation may perform an arbitrary action on the host system. This issue has its root in how runc handles Config Annotations lists. OWASP Top Ten 2017 Category A9 - Using Components with Known Vulnerabilities Affected range <=v1.1.4 Fixed version Not Fixed CVSS Score 7 CVSS Vector CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H Description runc through 1.1.4 has Incorrect Access Control leading to Escalation of Privileges, related to libcontainer/rootfs_linux.go. To exploit this, an attacker must be able to spawn two containers with custom volume-mount configurations, and be able to run custom images. NOTE: this issue exists because of a CVE-2019-19921 regression. Improper Preservation of Permissions Affected range <1.1.5 Fixed version 1.1.5 CVSS Score 6.1 CVSS Vector CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L Description Impact It was found that AppArmor, and potentially SELinux, can be bypassed when /proc inside the container is symlinked with a specific mount configuration. Patches Fixed in runc v1.1.5, by prohibiting symlinked /proc: opencontainers/runc#3785 This PR fixes CVE-2023-27561 as well. Workarounds Avoid using an untrusted container image. Incorrect Default Permissions Affected range <1.1.2 Fixed version 1.1.2 CVSS Score 5.9 CVSS Vector CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L Description Impact A bug was found in runc where runc exec --cap executed processes with non-empty inheritable Linux process capabilities, creating an atypical Linux environment and enabling programs with inheritable file capabilities to elevate those capabilities to the permitted set during execve(2). This bug did not affect the container security sandbox as the inheritable set never contained more capabilities than were included in the container's bounding set. Patches This bug has been fixed in runc 1.1.2. Users should update to this version as soon as possible. This fix changes runc exec --cap behavior such that the additional capabilities granted to the process being executed (as specified via --cap arguments) do not include inheritable capabilities. In addition, runc spec is changed to not set any inheritable capabilities in the created example OCI spec (config.json) file. Credits The opencontainers project would like to thank Andrew G. Morgan for responsibly disclosing this issue in accordance with the opencontainers org security policy. For more information If you have any questions or comments about this advisory: Open an issue Email us at security@opencontainers.org if you think you’ve found a security bug Improper Preservation of Permissions Affected range <1.1.5 Fixed version 1.1.5 CVSS Score 2.5 CVSS Vector CVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:C/C:N/I:N/A:L Description Impact It was found that rootless runc makes /sys/fs/cgroup writable in following conditons: when runc is executed inside the user namespace, and the config.json does not specify the cgroup namespace to be unshared (e.g.., (docker|podman|nerdctl) run --cgroupns=host, with Rootless Docker/Podman/nerdctl) or, when runc is executed outside the user namespace, and /sys is mounted with rbind, ro (e.g., runc spec --rootless; this condition is very rare) A container may gain the write access to user-owned cgroup hierarchy /sys/fs/cgroup/user.slice/... on the host . Other users's cgroup hierarchies are not affected. Patches v1.1.5 (planned) Workarounds Condition 1: Unshare the cgroup namespace ((docker|podman|nerdctl) run --cgroupns=private). This is the default behavior of Docker/Podman/nerdctl on cgroup v2 hosts. Condition 2 (very rare): add /sys/fs/cgroup to maskedPaths

[github-actions]

Attempting automerge. See https://github.com/uniget-org/tools/actions/runs/10219039249.

[github-actions]

PR is clean and can be merged. See https://github.com/uniget-org/tools/actions/runs/10219039249.