Bump github.com/containers/podman/v5 from 5.1.2 to 5.2.0

[dependabot]

Bumps github.com/containers/podman/v5 from 5.1.2 to 5.2.0.

Release notes

Sourced from github.com/containers/podman/v5's releases.

v5.2.0

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).

... (truncated)

Changelog

Sourced from github.com/containers/podman/v5's changelog.

Release Notes

5.1.0

Features

• VMs created by podman machine on macOS with Apple silicon can now use Rosetta 2 (a.k.a Rosetta) for high-speed emulation of x86 code. This is enabled by default. If you wish to change this option, you can do so in containers.conf.
• Changes made by the podman update command are now persistent, and will survive container restart and be reflected in podman inspect.
• The podman update command now includes a new option, --restart, to update the restart policy of existing containers.
• Quadlet .container files now support a new key, GroupAdd, to add groups to the container.
• Container annotations are now printed by podman inspect.
• Image-based mounts using podman run --mount type=image,... now support a new option, subpath, to mount only part of the image into the container.
• A new field, healthcheck_events, has been added to containers.conf under the [engine] section to allow users to disable the generation of health_status events to avoid spamming logs on systems with many healthchecks.
• A list of images to automatically mount as volumes can now be specified in Kubernetes YAML via the io.podman.annotations.kube.image.automount/$CTRNAME annotation (where $CTRNAME is the name of the container they will be mounted into).
• The podman info command now includes the default rootless network command (pasta or slirp4netns).
• The podman ps command now shows ports from --expose that have not been published with --publish-all to improve Docker compatibility.
• The podman container runlabel command now expands $HOME in the label being run to the user's home directory.
• A new alias, podman network list, has been added to the podman network ls command.
• The name and shell of containers created by podmansh can now be set in containers.conf.
• The podman-setup.exe Windows installer now provides 3 new CLI variables, MachineProvider (choose the provider for the machine, windows or wsl, the default), HyperVCheckbox (can be set to 1 to install HyperV if it is not already installed or 0, the default, to not install HyperV), and SkipConfigFileCreation (can be set to 1 to disable the creation of configuration files, or 0, the default).

Changes

• Podman now changes volume ownership every time an empty named volume is mounted into a container, not just the first time, matching Docker's behavior.
• When running Kubernetes YAML with podman kube play that does not include an imagePullPolicy and does not set a tag for the image, the image is now always pulled (#21211).
• When running Kubernetes YAML with podman kube play, pod-level restart policies are now passed down to individual containers within the pod (#20903).
• The --runroot global option can now accept paths with lengths longer than 50 characters (#22272).
• Updating containers with the podman update command now emits an event.

Bugfixes

• Fixed a bug where the --userns=keep-id:uid=0 option to podman create and podman run would generate incorrect UID mappings and cause the container to fail to start (#22078).
• Fixed a bug where podman stats could report inaccurate percentages for very large or very small values (#22064).
• Fixed a bug where bind-mount volumes defaulted to rbind instead of bind, meaning recursive mounts were allowed by default (#22107).
• Fixed a bug where the podman machine rm -f command would fail to remove Hyper-V virtual machines if they were running.
• Fixed a bug where the podman ps --sync command could sometimes fail to properly update the status of containers.
• Fixed a bug where bind-mount volumes using the :idmap option would sometimes be inaccessible with rootless Podman (#22228).
• Fixed a bug where bind-mount volumes using the :U option would have their ownership changed to the owner of the directory in the image being mounted over (#22224).
• Fixed a bug where removing multiple containers, pods, or images with the --force option did not work when multiple arguments were given to the command and one of them did not exist (#21529).
• Fixed a bug where Podman did not properly clean up old cached Machine images.
• Fixed a bug where rapidly-restarting containers with healthchecks could sometimes fail to start their healthchecks after restarting.
• Fixed a bug where nested Podman could create its pause.pid file in an incorrect directory (#22327).
• Fixed a bug where Podman would panic if an OCI runtime was configured without associated paths in containers.conf (#22561).
• Fixed a bug where the podman kube down command would not respect the StopTimeout and StopSignal of containers that it stopped (#22397).
• Fixed a bug where Systemd-managed containers could be stuck in the Stopping state, unable to be restarted, if systemd killed the unit before podman stop finished stopping the container (#19629).
• Fixed a bug where the remote Podman client's podman farm build command would not updating manifests on the registry that were already pushed (#22647).
• Fixed a bug where rootless Podman could fail to re-exec itself when run with a custom argv[0] that is not a valid command path, as might happen when used in podmansh (#22672).
• Fixed a bug where podman machine connection URIs could be incorrect after an SSH port conflict, rendering machines inaccessible.
• Fixed a bug where the podman events command would not print an error if incorrect values were passed to its --since and --until options.
• Fixed a bug where an incorrect host.containers.internal entry could be added when running rootless containers using the bridge network mode (#22653).

API

• A new Docker-compatible endpoint, Update, has been added for containers.
• The Compat Create endpoint for Containers now supports setting container annotations.

... (truncated)

Commits

• b22d5c6 Bump to v5.2.0
• 9331788 Merge pull request #23475 from openshift-cherrypick-robot/cherry-pick-23474-t...
• 3f13c38 Never skip checkout step in release workflow
• 8b246b6 Merge pull request #23462 from mheon/bump_520_rc3
• c83c891 Bump to v5.2.0-dev
• 028bee2 Bump to v5.2.0-rc3
• 23c6e0f Update release notes for v5.2.0-rc3
• 784856b Tweak versions in register_images.go
• d6ae742 fix network cleanup flake in play kube
• c0f3ce4 WIP: Fixes for vendoring Buildah
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[dependabot]

Superseded by #2172.