Bump github.com/containers/podman/v4 from 4.5.1 to 4.6.0

[dependabot]

Bumps github.com/containers/podman/v4 from 4.5.1 to 4.6.0.

Release notes

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

v4.6.0

Features

• The podman manifest inspect command now supports the --authfile option, for authentication purposes.
• The podman wait command now supports --condition={healthy,unhealthy}, allowing waits on successful health checks.
• The podman push command now supports a new option, --compression-level, which specifies the compression level to use (#18939).
• The podman machine start command, when run with --log-level=debug, now creates a console window to display the virtual machine while booting.
• Podman now supports a new option, --imagestore, which allows images to be stored in a different directory than the graphroot.
• The --ip-range option to the podman network create command now accepts a new syntax, <startIP>-<endIP>, which allows more flexibility when limiting the ip range that Podman assigns.
• [Tech Preview] A new command, podmansh, has been added, which executes a user shell within a container when the user logs into the system. The container that the users get added to can be defined via a Podman Quadlet file. This feature is currently a Tech Preview which means it's ready for users to try out but changes can be expected in upcoming versions.
• The podman network create command supports a new --option, bclim, for the macvlan driver.
• The podman network create command now supports adding static routes using the --route option.
• The podman network create command supports a new --option, no_default_route for all drivers.
• The podman info command now prints network information about the binary path, package version, program version and DNS information (#18443).
• The podman info command now displays the number of free locks available, helping to debug lock exhaustion scenarios.
• The podman info command now outputs information about pasta, if it exists in helper_binaries_dir or $PATH.
• The remote Podman client’s podman build command now accepts Containerfiles that are not in the context directory (#18239).
• The remote Podman client’s podman play kube command now supports the --configmap option (#17513).
• The podman kube play command now supports multi-doc YAML files for configmap arguments. (#18537).
• The podman pod create command now supports a new flag, --restart, which sets the restart policy for all the containers in a pod.
• The --format={{.Restarts}} option to the podman ps command now shows the number of times a container has been restarted based on its restart policy.
• The --format={{.Restarts}} option to the podman pod ps command now shows the total number of container restarts in a pod.
• The podman machine provider can now be specified via the CONTAINERS_MACHINE_PROVIDER environment variable, as well as via the provider field in containers.conf (#17116).
• A default list of pasta arguments can now be set in containers.conf via pasta_options.
• The podman machine init and podman machine set commands now support a new option, --user-mode-networking, which improves interops with VPN configs that drop traffic from WSL networking, on Windows.
• The remote Podman client’s podman push command now supports the --digestfile option (#18216).
• Podman now supports a new option, --out, that allows redirection or suppression of STDOUT (#18120).

Changes

• The podman system service command now emits a warning when binding to a TCP socket. This is not a secure configuration and the Podman team recommends against using it.
• The podman top command no longer depends on ps(1) being present in the container image and now uses the one from the host (#19001).
• The --filter id=xxx option will now treat xxx as a CID prefix, and not as a regular expression (#18471).
• The --filter option now requires multiple --filter flags to specify multiple filters. It will no longer support the comma syntax (--filter label=a,label=b).
• The slirp4netns binary for will now be searched for in paths specified by the helper_binaries_dir option in containers.conf (#18239).
• Podman machine now updates /run/docker.sock within the guest to be consistent with its rootless/rootful setting (#18480).
• The podman system df command now counts files which podman generates for use with specific containers as part of the disk space used by those containers, and which can be reclaimed by removing those containers. It also counts space used by files it associates with specific images and volumes as being used by those images and volumes.
• The podman build command now returns a clearer error message when the Containerfile cannot be found. (#16354).
• Containers created with --pid=host will no longer print errors on podman stop (#18460).
• The podman manifest push command no longer requires a destination to be specified. If a destination is not provided, the source is used as the destination (#18360).
• The podman system reset command now warns the user that the graphroot and runroot directories will be deleted (#18349), (#18295).
• The package and package-install targets in Makefile have now been fixed and also renamed to rpm and rpm-install respectively for clarity (#18817).

Quadlet

• Quadlet now exits with a non-zero exit code when errors are found (#18778).
• Rootless podman quadlet files can now be installed in /etc/containers/systemd/users directory.
• Quadlet now supports the AutoUpdate option.
• Quadlet now supports the Mask and Unmask options.
• Quadlet now supports the WorkingDir option, which specifies the default working dir in a container.
• Quadlet now supports the Sysctl option, which sets namespaced kernel parameters for containers (#18727).
• Quadlet now supports the SecurityLabelNetsted=true option, which allows nested SELinux containers.
• Quadlet now supports the Pull option in .container files (#18779).

... (truncated)

Changelog

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

4.6.0

Features

• The podman manifest inspect command now supports the --authfile option, for authentication purposes.
• The podman wait command now supports --condition={healthy,unhealthy}, allowing waits on successful health checks.
• The podman push command now supports a new option, --compression-level, which specifies the compression level to use (#18939).
• The podman machine start command, when run with --log-level=debug, now creates a console window to display the virtual machine while booting.
• Podman now supports a new option, --imagestore, which allows images to be stored in a different directory than the graphroot.
• The --ip-range option to the podman network create command now accepts a new syntax, <startIP>-<endIP>, which allows more flexibility when limiting the ip range that Podman assigns.
• [Tech Preview] A new command, podmansh, has been added, which executes a user shell within a container when the user logs into the system. The container that the users get added to can be defined via a Podman Quadlet file. This feature is currently a Tech Preview which means it's ready for users to try out but changes can be expected in upcoming versions.
• The podman network create command supports a new --option, bclim, for the macvlan driver.
• The podman network create command now supports adding static routes using the --route option.
• The podman network create command supports a new --option, no_default_route for all drivers.
• The podman info command now prints network information about the binary path, package version, program version and DNS information (#18443).
• The podman info command now displays the number of free locks available, helping to debug lock exhaustion scenarios.
• The podman info command now outputs information about pasta, if it exists in helper_binaries_dir or $PATH.
• The remote Podman client’s podman build command now accepts Containerfiles that are not in the context directory (#18239).
• The remote Podman client’s podman play kube command now supports the --configmap option (#17513).
• The podman kube play command now supports multi-doc YAML files for configmap arguments. (#18537).
• The podman pod create command now supports a new flag, --restart, which sets the restart policy for all the containers in a pod.
• The --format={{.Restarts}} option to the podman ps command now shows the number of times a container has been restarted based on its restart policy.
• The --format={{.Restarts}} option to the podman pod ps command now shows the total number of container restarts in a pod.
• The podman machine provider can now be specified via the CONTAINERS_MACHINE_PROVIDER environment variable, as well as via the provider field in containers.conf (#17116).
• A default list of pasta arguments can now be set in containers.conf via pasta_options.
• The podman machine init and podman machine set commands now support a new option, --user-mode-networking, which improves interops with VPN configs that drop traffic from WSL networking, on Windows.
• The remote Podman client’s podman push command now supports the --digestfile option (#18216).
• Podman now supports a new option, --out, that allows redirection or suppression of STDOUT (#18120).

Changes

• The podman system service command now emits a warning when binding to a TCP socket. This is not a secure configuration and the Podman team recommends against using it.
• The podman top command no longer depends on ps(1) being present in the container image and now uses the one from the host (#19001).
• The --filter id=xxx option will now treat xxx as a CID prefix, and not as a regular expression (#18471).
• The --filter option now requires multiple --filter flags to specify multiple filters. It will no longer support the comma syntax (--filter label=a,label=b).
• The slirp4netns binary for will now be searched for in paths specified by the helper_binaries_dir option in containers.conf (#18239).
• Podman machine now updates /run/docker.sock within the guest to be consistent with its rootless/rootful setting (#18480).
• The podman system df command now counts files which podman generates for use with specific containers as part of the disk space used by those containers, and which can be reclaimed by removing those containers. It also counts space used by files it associates with specific images and volumes as being used by those images and volumes.
• The podman build command now returns a clearer error message when the Containerfile cannot be found. (#16354).
• Containers created with --pid=host will no longer print errors on podman stop (#18460).
• The podman manifest push command no longer requires a destination to be specified. If a destination is not provided, the source is used as the destination (#18360).
• The podman system reset command now warns the user that the graphroot and runroot directories will be deleted (#18349), (#18295).
• The package and package-install targets in Makefile have now been fixed and also renamed to rpm and rpm-install respectively for clarity (#18817).

Quadlet

• Quadlet now exits with a non-zero exit code when errors are found (#18778).
• Rootless podman quadlet files can now be installed in /etc/containers/systemd/users directory.
• Quadlet now supports the AutoUpdate option.
• Quadlet now supports the Mask and Unmask options.
• Quadlet now supports the WorkingDir option, which specifies the default working dir in a container.
• Quadlet now supports the Sysctl option, which sets namespaced kernel parameters for containers (#18727).
• Quadlet now supports the SecurityLabelNetsted=true option, which allows nested SELinux containers.
• Quadlet now supports the Pull option in .container files (#18779).

... (truncated)

Commits

• 38e6fab Bump to v4.6.0
• 8aec599 Update release notes for v4.6.0
• 09b1da3 Ensure that we appropriately warn that TCP is insecure
• 0115a48 CI: remove build without cgo task
• 598ebe8 libpod: use io.Writer vs io.WriteCloser for attach streams
• 574b782 top: do not depend on ps(1) in container
• 2551112 api: fix doc for default ps_args
• 34274ce Add more tests for liveness probes with default hostname & named ports
• 48deafc Fix TCP probes when the optional host field is not given
• 6817e0a Add support for using port names in Kubernetes health probes
• 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 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

Merging #1479 (6043bc7) into main (54295f7) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main    #1479   +/-   ##
=======================================
  Coverage   21.83%   21.83%           
=======================================
  Files          65       65           
  Lines        6809     6809           
=======================================
  Hits         1487     1487           
  Misses       5191     5191           
  Partials      131      131