build(deps): bump github.com/containers/podman/v3 from 3.2.2 to 3.4.2

[dependabot]

Bumps github.com/containers/podman/v3 from 3.2.2 to 3.4.2.

Release notes

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

v3.4.2

Bugfixes

• Fixed a bug where podman tag could not tag manifest lists (#12046).
• Fixed a bug where built-in volumes specified by images would not be created correctly under some circumstances.
• Fixed a bug where, when using Podman Machine on OS X, containers in pods did not have working port forwarding from the host (#12207).
• Fixed a bug where the podman network reload command command on containers using the slirp4netns network mode and the rootlessport port forwarding driver would make an unnecessary attempt to restart rootlessport on containers that did not forward ports.
• Fixed a bug where the podman generate kube command would generate YAML including some unnecessary (set to default) fields (e.g. empty SELinux and DNS configuration blocks, and the privileged flag when set to false) (#11995).
• Fixed a bug where the podman pod rm command could, if interrupted at the right moment, leave a reference to an already-removed infra container behind (#12034).
• Fixed a bug where the podman pod rm command would not remove pods with more than one container if all containers save for the infra container were stopped unless --force was specified (#11713).
• Fixed a bug where the --memory flag to podman run and podman create did not accept a limit of 0 (which should specify unlimited memory) (#12002).
• Fixed a bug where the remote Podman client's podman build command could attempt to build a Dockerfile in the working directory of the podman system service instance instead of the Dockerfile specified by the user (#12054).
• Fixed a bug where the podman logs --tail command could function improperly (printing more output than requested) when the journald log driver was used.
• Fixed a bug where containers run using the slirp4netns network mode with IPv6 enabled would not have IPv6 connectivity until several seconds after they started (#11062).
• Fixed a bug where some Podman commands could cause an extra dbus-daemon process to be created (#9727).
• Fixed a bug where rootless Podman would sometimes print warnings about a failure to move the pause process into a given CGroup (#12065).
• Fixed a bug where the checkpointed field in podman inspect on a container was not set to false after a container was restored.
• Fixed a bug where the podman system service command would print overly-verbose logs about request IDs (#12181).
• Fixed a bug where Podman could, when creating a new container without a name explicitly specified by the user, sometimes use an auto-generated name already in use by another container if multiple containers were being created in parallel (#11735).

v3.4.1

Bugfixes

• Fixed a bug where podman machine init could, under some circumstances, create invalid machine configurations which could not be started (#11824).
• Fixed a bug where the podman machine list command would not properly populate some output fields.
• Fixed a bug where podman machine rm could leave dangling sockets from the removed machine (#11393).
• Fixed a bug where podman run --pids-limit=-1 was not supported (it now sets the PID limit in the container to unlimited) (#11782).
• Fixed a bug where podman run and podman attach could throw errors about a closed network connection when STDIN was closed by the client (#11856).
• Fixed a bug where the podman stop command could fail when run on a container that had another podman stop command run on it previously.
• Fixed a bug where the --sync flag to podman ps was nonfunctional.
• Fixed a bug where the Windows and OS X remote clients' podman stats command would fail (#11909).
• Fixed a bug where the podman play kube command did not properly handle environment variables whose values contained an = (#11891).
• Fixed a bug where the podman generate kube command could generate invalid annotations when run on containers with volumes that use SELinux relabelling (:z or :Z) (#11929).
• Fixed a bug where the podman generate kube command would generate YAML including some unnecessary (set to default) fields (e.g. user and group, entrypoint, default protocol for forwarded ports) (#11914, #11915, and #11965).
• Fixed a bug where the podman generate kube command could, under some circumstances, generate YAML including an invalid targetPort field for forwarded ports (#11930).
• Fixed a bug where rootless Podman's podman info command could, under some circumstances, not read available CGroup controllers (#11931).
• Fixed a bug where podman container checkpoint --export would fail to checkpoint any container created with --log-driver=none (#11974).

API

• Fixed a bug where the Compat Create endpoint for Containers could panic when no options were passed to a bind mount of tmpfs (#11961).

v3.4.0

Features

• Pods now support init containers! Init containers are containers which run before the rest of the pod starts. There are two types of init containers: "always", which always run before the pod is started, and "once", which only run the first time the pod starts and are subsequently removed. They can be added using the podman create command's --init-ctr option.
• Support for init containers has also been added to podman play kube and podman generate kube - init containers contained in Kubernetes YAML will be created as Podman init containers, and YAML generated by Podman will include any init containers created.
• The podman play kube command now supports building images. If the --build option is given and a directory with the name of the specified image exists in the current working directory and contains a valid Containerfile or Dockerfile, the image will be built and used for the container.
• The podman play kube command now supports a new option, --down, which removes any pods and containers created by the given Kubernetes YAML.
• The podman generate kube command now generates annotations for SELinux mount options on volume (:z and :Z) that are respected by the podman play kube command.
• A new command has been added, podman pod logs, to return logs for all containers in a pod at the same time.
• Two new commands have been added, podman volume export (to export a volume to a tar file) and podman volume import) (to populate a volume from a given tar file).
• The podman auto-update command now supports simple rollbacks. If a container fails to start after an automatic update, it will be rolled back to the previous image and restarted again.
• Pods now share their user namespace by default, and the podman pod create command now supports the --userns option. This allows rootless pods to be created with the --userns=keep-id option.

... (truncated)

Changelog

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

3.4.2

Bugfixes

• Fixed a bug where podman tag could not tag manifest lists (#12046).
• Fixed a bug where built-in volumes specified by images would not be created correctly under some circumstances.
• Fixed a bug where, when using Podman Machine on OS X, containers in pods did not have working port forwarding from the host (#12207).
• Fixed a bug where the podman network reload command command on containers using the slirp4netns network mode and the rootlessport port forwarding driver would make an unnecessary attempt to restart rootlessport on containers that did not forward ports.
• Fixed a bug where the podman generate kube command would generate YAML including some unnecessary (set to default) fields (e.g. empty SELinux and DNS configuration blocks, and the privileged flag when set to false) (#11995).
• Fixed a bug where the podman pod rm command could, if interrupted at the right moment, leave a reference to an already-removed infra container behind (#12034).
• Fixed a bug where the podman pod rm command would not remove pods with more than one container if all containers save for the infra container were stopped unless --force was specified (#11713).
• Fixed a bug where the --memory flag to podman run and podman create did not accept a limit of 0 (which should specify unlimited memory) (#12002).
• Fixed a bug where the remote Podman client's podman build command could attempt to build a Dockerfile in the working directory of the podman system service instance instead of the Dockerfile specified by the user (#12054).
• Fixed a bug where the podman logs --tail command could function improperly (printing more output than requested) when the journald log driver was used.
• Fixed a bug where containers run using the slirp4netns network mode with IPv6 enabled would not have IPv6 connectivity until several seconds after they started (#11062).
• Fixed a bug where some Podman commands could cause an extra dbus-daemon process to be created (#9727).
• Fixed a bug where rootless Podman would sometimes print warnings about a failure to move the pause process into a given CGroup (#12065).
• Fixed a bug where the checkpointed field in podman inspect on a container was not set to false after a container was restored.
• Fixed a bug where the podman system service command would print overly-verbose logs about request IDs (#12181).
• Fixed a bug where Podman could, when creating a new container without a name explicitly specified by the user, sometimes use an auto-generated name already in use by another container if multiple containers were being created in parallel (#11735).

3.4.1

Bugfixes

• Fixed a bug where podman machine init could, under some circumstances, create invalid machine configurations which could not be started (#11824).
• Fixed a bug where the podman machine list command would not properly populate some output fields.
• Fixed a bug where podman machine rm could leave dangling sockets from the removed machine (#11393).
• Fixed a bug where podman run --pids-limit=-1 was not supported (it now sets the PID limit in the container to unlimited) (#11782).
• Fixed a bug where podman run and podman attach could throw errors about a closed network connection when STDIN was closed by the client (#11856).
• Fixed a bug where the podman stop command could fail when run on a container that had another podman stop command run on it previously.
• Fixed a bug where the --sync flag to podman ps was nonfunctional.
• Fixed a bug where the Windows and OS X remote clients' podman stats command would fail (#11909).
• Fixed a bug where the podman play kube command did not properly handle environment variables whose values contained an = (#11891).
• Fixed a bug where the podman generate kube command could generate invalid annotations when run on containers with volumes that use SELinux relabelling (:z or :Z) (#11929).
• Fixed a bug where the podman generate kube command would generate YAML including some unnecessary (set to default) fields (e.g. user and group, entrypoint, default protocol for forwarded ports) (#11914, #11915, and #11965).
• Fixed a bug where the podman generate kube command could, under some circumstances, generate YAML including an invalid targetPort field for forwarded ports (#11930).
• Fixed a bug where rootless Podman's podman info command could, under some circumstances, not read available CGroup controllers (#11931).
• Fixed a bug where podman container checkpoint --export would fail to checkpoint any container created with --log-driver=none (#11974).

API

• Fixed a bug where the Compat Create endpoint for Containers could panic when no options were passed to a bind mount of tmpfs (#11961).

3.4.0

Features

• Pods now support init containers! Init containers are containers which run before the rest of the pod starts. There are two types of init containers: "always", which always run before the pod is started, and "once", which only run the first time the pod starts and are subsequently removed. They can be added using the podman create command's --init-ctr option.
• Support for init containers has also been added to podman play kube and podman generate kube - init containers contained in Kubernetes YAML will be created as Podman init containers, and YAML generated by Podman will include any init containers created.
• The podman play kube command now supports building images. If the --build option is given and a directory with the name of the specified image exists in the current working directory and contains a valid Containerfile or Dockerfile, the image will be built and used for the container.
• The podman play kube command now supports a new option, --teardown, which removes any pods and containers created by the given Kubernetes YAML.
• The podman generate kube command now generates annotations for SELinux mount options on volume (:z and :Z) that are respected by the podman play kube command.
• A new command has been added, podman pod logs, to return logs for all containers in a pod at the same time.
• Two new commands have been added, podman volume export (to export a volume to a tar file) and podman volume import) (to populate a volume from a given tar file).
• The podman auto-update command now supports simple rollbacks. If a container fails to start after an automatic update, it will be rolled back to the previous image and restarted again.
• Pods now share their user namespace by default, and the podman pod create command now supports the --userns option. This allows rootless pods to be created with the --userns=keep-id option.

... (truncated)

Commits

• 2ad1fd3 Bump to v3.4.2
• 1d6397e Add release notes for v3.4.2
• 6d9b1e4 Fix partial log line handling with journald log driver
• 8b368b5 Fix Zsh completion command documentation
• c2fb170 Fix flake in upgrade tests
• 6770fed VOLUME must be declared after RUN chown command
• cedf1a3 podman-generate-kube - remove empty structs from YAML
• e456873 Exclude already built sources for static build
• e9f6e51 Match .c files in Makefile
• de852eb shm_lock: Handle ENOSPC better in AllocateSemaphore
• 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]

The following labels could not be found: release-note-none.

[dependabot]

Superseded by #53.