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

[dependabot]

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

Release notes

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

v4.6.1

Quadlet

• Quadlet now selects the first Quadlet file found when multiple Quadlets exist with the same name.

API

• Fixed a bug in the container kill endpoint to correctly return 409 when a container is not running (#19368).

Misc

• Updated Buildah to v1.31.2
• Updated the containers/common library to v0.55.3

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

• When looking up an image by digest, the entire repository of the specified value is now considered. This aligns with Docker's behavior since v20.10.20. Previously, both the repository and the tag was ignored and Podman looked for an image with only a matching digest. Ignoring the name, repository, and tag of the specified value can lead to security issues and is considered harmful.
• 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).

... (truncated)

Changelog

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

4.6.1

Quadlet

• Quadlet now selects the first Quadlet file found when multiple Quadlets exist with the same name.

API

• Fixed a bug in the container kill endpoint to correctly return 409 when a container is not running (#19368).

Misc

• Updated Buildah to v1.31.2
• Updated the containers/common library to v0.55.3

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

... (truncated)

Commits

• f3069b3 Bump to v4.6.1
• 57bdc5e Release notes for v4.6.1
• 3c7c856 Vendor buildah v1.31.2
• 1425dce Merge pull request #19584 from vrothberg/4.6-vendor-common
• 50501a9 [4.6] vendor c/common v0.55.3
• 7de8fda Merge pull request #19553 from TomSweeneyRedHat/dev/tsweeney/nochunked
• 2d02865 [v4.6] Remove zstd:chunked reference
• 3ecd29f Merge pull request #19536 from lsm5/v4.6-cve-2023-3978
• ef9747c [v4.6] bump golang.org/x/net to v0.13.0
• 2215847 Merge pull request #19473 from edsantiago/openqa_v46
• 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]

OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version or @dependabot ignore this minor version. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.