Bump github.com/containers/podman/v5 from 5.0.3 to 5.1.1

[dependabot]

Bumps github.com/containers/podman/v5 from 5.0.3 to 5.1.1.

Release notes

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

v5.1.1

Bugfixes

• Fixed a bug where systemd timers associated with startup healthchecks would not be properly deleted after transitioning to the regular healthcheck (#22884).

Misc

• Updated the containers/common library to v0.59.1

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

... (truncated)

Changelog

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

5.1.1

Bugfixes

• Fixed a bug where systemd timers associated with startup healthchecks would not be properly deleted after transitioning to the regular healthcheck (#22884).

Misc

• Updated the containers/common library to v0.59.1

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 use the CONTAINERS_MACHINE_ROSETTA environment variable or 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 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.

... (truncated)

Commits

• bda6eb0 Bump to v5.1.1
• cd0a0d7 Update release notes for v5.1.1
• aa031ad libpod: do not leak systemd hc startup unit timer
• d79b94c Check AppleHypervisor before accessing it
• db5393f Merge pull request #22894 from TomSweeneyRedHat/dev/tsweeney/common_0.59.1_v5.1
• a9377a8 [v5.1] Bump c/common to v0.59.1
• 4dc75c6 [v5.1] pkg/rootless: set _CONTAINERS_USERNS_CONFIGURED
• 5359846 Merge pull request #22892 from openshift-cherrypick-robot/cherry-pick-22880-t...
• 9a19ca6 Merge pull request #22890 from cevich/v5.1_cp_22773
• d5cc37f test/e2e: use local skopeo not image
• 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)

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 53.77%. Comparing base (657bf98) to head (b3d9d11).
Report is 1 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #2065      +/-   ##
==========================================
+ Coverage   53.73%   53.77%   +0.04%     
==========================================
  Files         160      160              
  Lines       11524    11524              
==========================================
+ Hits         6192     6197       +5     
+ Misses       4465     4461       -4     
+ Partials      867      866       -1     

Files	Coverage Δ
runtime/docker/docker.go	72.07% <100.00%> (ø)

... and 1 file with indirect coverage changes