Bump github.com/containers/podman/v4 from 4.3.0 to 4.4.1

[dependabot]

Bumps github.com/containers/podman/v4 from 4.3.0 to 4.4.1.

Release notes

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

v4.4.1

Changes

• Added the podman-systemd.unit man page, which can also be displayed using man quadlet (#17349).
• Documented journald identifiers used in the journald backend for the podman events command.

Bugfixes

• Fixed a bug where the default handling of pids-limit was incorrect.
• Fixed a bug where parallel calls to make docs crashed (#17322).
• Fixed a regression in the podman kube play command where existing resources got mistakenly removed.

v4.4.0

Features

• Introduce Quadlet, a new systemd-generator that easily writes and maintains systemd services using Podman.
• The podman kube play command now supports hostPID in the pod.spec (#17157).
• The podman build command now supports the --group-add option.
• A new command, podman network update has been added, which updates networks for containers and pods.
• The podman network create command now supports a new option, --network-dns-server, which sets the DNS servers that this network will use.
• The podman kube play command now accepts the--publish option, which sets or overrides port publishing.
• The podman inspect command now returns an error field (#13729).
• The podman update command now accepts the --pids-limit option, which sets the PIDs limit for a container (#16543).
• Podman now supports container names beginning with a / to match Docker behaviour (#16663).
• The podman events command now supports die as a value (mapping to died) to the --filter option, for better Docker compatibility (#16857).
• The podman system dfcommand’s --format "{{ json . }}" option now outputs human-readable format to improve Docker compatibility
• The podman rm -f command now also terminates containers in "stopping" state.
• Rootless privileged containers will now mount all tty devices, except for the virtual-console related tty devices (/dev/tty[0-9]+) (#16925).
• The podman play kube command now supports subpaths when using configmap and hostpath volume types (#16828).
• All commands with the --no-heading option now include a short option, -n.
• The podman push command no longer ignores the hidden --signature-policy flag.
• The podman wait command now supports the --ignore option.
• The podman network create command now supports the --ignore option to instruct Podman to not fail when trying to create an already existing network.
• The podman kube play command now supports volume subpaths when using named volumes (#12929).
• The podman kube play command now supports container startup probes.
• A new command, podman buildx version, has been added, which shows the buildah version (#16793).
• Remote usage of the podman build command now supports the --volume option (#16694).
• The --opt parent=... option is now accepted with the ipvlan network driver in the podman network create command (#16621).
• The --init-ctr option for the podman container create command now supports shell completion.
• The podman kube play command run with a readOnlyTmpfs Flag in the kube YAML can now write to tmpfs inside of the container.
• The podman run command has been extended with support for checkpoint images.
• When the new event_audit_container_create option is enabled in containers.conf, the verbosity of the container-create event is increased by adding the inspect data of the container to the event.
• Containers can now have startup healthchecks, allowing a command to be run to ensure the container is fully started before the regular healthcheck is activated.
• CDI devices can now be specified in containers.conf (#16232).
• The podman push command features two new options, --encryption-key and --encrypt-layer, for encrypting an image while pushing it to a registry (#15163).
• The podman pull and podman run commands feature a new option, --decryption-key, which decrypts the image while pulling it from a registry (#15163).
• Remote usage of the podman manifest annotate command is now supported.
• The SSL_CERT_FILE and SSL_CERT_DIR environment variables are now propagated into Podman machine VMs (#16041).
• A new environment variable, CONTAINER_PROXY, can be used to specify TCP proxies when using remote Podman.
• The runtime automatically detects and switches to crun-wasm if the image is a webassembly image.
• The podman machine init command now supports the --quiet option, as well a new option, --no-info which suppresses informational tips (#15525).
• The podman volume create command now includes the -d short option for the --driver option.
• The podman events command has a new alias, podman system events, for better Docker compatibility.

... (truncated)

Changelog

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

4.4.1

Changes

• Added the podman-systemd.unit man page, which can also be displayed using man quadlet (#17349).
• Documented journald identifiers used in the journald backend for the podman events command.

Bugfixes

• Fixed a bug where the default handling of pids-limit was incorrect.
• Fixed a bug where parallel calls to make docs crashed (#17322).
• Fixed a regression in the podman kube play command where existing resources got mistakenly removed.

4.4.0

Features

• Introduce Quadlet, a new systemd-generator that easily writes and maintains systemd services using Podman.
• The podman kube play command now supports hostPID in the pod.spec (#17157).
• The podman build command now supports the --group-add option.
• A new command, podman network update has been added, which updates networks for containers and pods.
• The podman network create command now supports a new option, --network-dns-server, which sets the DNS servers that this network will use.
• The podman kube play command now accepts the--publish option, which sets or overrides port publishing.
• The podman inspect command now returns an error field (#13729).
• The podman update command now accepts the --pids-limit option, which sets the PIDs limit for a container (#16543).
• Podman now supports container names beginning with a / to match Docker behaviour (#16663).
• The podman events command now supports die as a value (mapping to died) to the --filter option, for better Docker compatibility (#16857).
• The podman system dfcommand’s --format "{{ json . }}" option now outputs human-readable format to improve Docker compatibility
• The podman rm -f command now also terminates containers in "stopping" state.
• Rootless privileged containers will now mount all tty devices, except for the virtual-console related tty devices (/dev/tty[0-9]+) (#16925).
• The podman play kube command now supports subpaths when using configmap and hostpath volume types (#16828).
• All commands with the --no-heading option now include a short option, -n.
• The podman push command no longer ignores the hidden --signature-policy flag.
• The podman wait command now supports the --ignore option.
• The podman network create command now supports the --ignore option to instruct Podman to not fail when trying to create an already existing network.
• The podman kube play command now supports volume subpaths when using named volumes (#12929).
• The podman kube play command now supports container startup probes.
• A new command, podman buildx version, has been added, which shows the buildah version (#16793).
• Remote usage of the podman build command now supports the --volume option (#16694).
• The --opt parent=... option is now accepted with the ipvlan network driver in the podman network create command (#16621).
• The --init-ctr option for the podman container create command now supports shell completion.
• The podman kube play command run with a readOnlyTmpfs Flag in the kube YAML can now write to tmpfs inside of the container.
• The podman run command has been extended with support for checkpoint images.
• When the new event_audit_container_create option is enabled in containers.conf, the verbosity of the container-create event is increased by adding the inspect data of the container to the event.
• Containers can now have startup healthchecks, allowing a command to be run to ensure the container is fully started before the regular healthcheck is activated.
• CDI devices can now be specified in containers.conf (#16232).
• The podman push command features two new options, --encryption-key and --encrypt-layer, for encrypting an image while pushing it to a registry (#15163).
• The podman pull and podman run commands feature a new option, --decryption-key, which decrypts the image while pulling it from a registry (#15163).
• Remote usage of the podman manifest annotate command is now supported.
• The SSL_CERT_FILE and SSL_CERT_DIR environment variables are now propagated into Podman machine VMs (#16041).
• A new environment variable, CONTAINER_PROXY, can be used to specify TCP proxies when using remote Podman.
• The runtime automatically detects and switches to crun-wasm if the image is a webassembly image.
• The podman machine init command now supports the --quiet option, as well a new option, --no-info which suppresses informational tips (#15525).
• The podman volume create command now includes the -d short option for the --driver option.
• The podman events command has a new alias, podman system events, for better Docker compatibility.

... (truncated)

Commits

• 34e8f39 Bump to v4.4.1
• 7431f3d Update release notes for Podman 4.4.1
• 1bde07e Merge pull request #17429 from openshift-cherrypick-robot/cherry-pick-17027-t...
• 393336b Merge pull request #17430 from openshift-cherrypick-robot/cherry-pick-17420-t...
• db50458 Merge pull request #17390 from openshift-cherrypick-robot/cherry-pick-17364-t...
• 68a58c9 kube play: do not teardown unconditionally on error
• 7b5f724 Merge pull request #17404 from openshift-cherrypick-robot/cherry-pick-17351-t...
• a1cc373 Resolve symlink path for qemu directory if possible
• f5670f0 Merge pull request #17371 from openshift-cherrypick-robot/cherry-pick-17356-t...
• 5571faa Merge pull request #17408 from openshift-cherrypick-robot/cherry-pick-17293-t...
• 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)

[dependabot]

Superseded by #22.