Thanks to visit codestin.com
Credit goes to github.com

Skip to content

build(deps): bump github.com/containers/podman/v3 from 3.3.1 to 3.4.1 #5416

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Merged
openshift-merge-robot merged 1 commit into from
Oct 20, 2021
Merged

build(deps): bump github.com/containers/podman/v3 from 3.3.1 to 3.4.1 #5416

openshift-merge-robot merged 1 commit into from
Oct 20, 2021

Conversation

@dependabot
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Oct 20, 2021

Bumps github.com/containers/podman/v3 from 3.3.1 to 3.4.1.

Release notes

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

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.
  • The podman pod ps command now supports a new filter with its --filter option, until, which returns pods created before a given timestamp.
  • The podman image scp command has been added. This command allows images to be transferred between different hosts.
  • The podman stats command supports a new option, --interval, to specify the amount of time before the information is refreshed.
  • The podman inspect command now includes ports exposed (but not published) by containers (e.g. ports from --expose when --publish-all is not specified).
  • The podman inspect command now has a new boolean value, Checkpointed, which indicates that a container was stopped as a result of a podman container checkpoint operation.
  • Volumes created by podman volume create now support setting quotas when run atop XFS. The size and inode options allow the maximum size and maximum number of inodes consumed by a volume to be limited.
  • The podman info command now outputs information on what log drivers, network drivers, and volume plugins are available for use (#11265).
  • The podman info command now outputs the current log driver in use, and the variant and codename of the distribution in use.
  • The parameters of the VM created by podman machine init (amount of disk space, memory, CPUs) can now be set in containers.conf.
  • The podman machine ls command now shows additional information (CPUs, memory, disk size) about VMs managed by podman machine.
  • The podman ps command now includes healthcheck status in container state for containers that have healthchecks (#11527).

Changes

  • The podman build command has a new alias, podman buildx, to improve compatibility with Docker. We have already added support for many docker buildx flags to podman build and aim to continue to do so.
  • Cases where Podman is run without a user session or a writable temporary files directory will now produce better error messages.
  • The default log driver has been changed from file to journald. The file driver did not properly support log rotation, so this should lead to a better experience. If journald is not available on the system, Podman will automatically revert to the file.
  • Podman no longer depends on ip for removing networks (#11403).
  • The deprecated --macvlan flag to podman network create now warns when it is used. It will be removed entirely in the Podman 4.0 release.
  • The podman machine start command now prints a message when the VM is successfully started.

... (truncated)

Changelog

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

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.
  • The podman pod ps command now supports a new filter with its --filter option, until, which returns pods created before a given timestamp.
  • The podman image scp command has been added. This command allows images to be transferred between different hosts.
  • The podman stats command supports a new option, --interval, to specify the amount of time before the information is refreshed.
  • The podman inspect command now includes ports exposed (but not published) by containers (e.g. ports from --expose when --publish-all is not specified).
  • The podman inspect command now has a new boolean value, Checkpointed, which indicates that a container was stopped as a result of a podman container checkpoint operation.
  • Volumes created by podman volume create now support setting quotas when run atop XFS. The size and inode options allow the maximum size and maximum number of inodes consumed by a volume to be limited.
  • The podman info command now outputs information on what log drivers, network drivers, and volume plugins are available for use (#11265).
  • The podman info command now outputs the current log driver in use, and the variant and codename of the distribution in use.
  • The parameters of the VM created by podman machine init (amount of disk space, memory, CPUs) can now be set in containers.conf.
  • The podman machine ls command now shows additional information (CPUs, memory, disk size) about VMs managed by podman machine.
  • The podman ps command now includes healthcheck status in container state for containers that have healthchecks (#11527).

Changes

  • The podman build command has a new alias, podman buildx, to improve compatibility with Docker. We have already added support for many docker buildx flags to podman build and aim to continue to do so.
  • Cases where Podman is run without a user session or a writable temporary files directory will now produce better error messages.
  • The default log driver has been changed from file to journald. The file driver did not properly support log rotation, so this should lead to a better experience. If journald is not available on the system, Podman will automatically revert to the file.
  • Podman no longer depends on ip for removing networks (#11403).
  • The deprecated --macvlan flag to podman network create now warns when it is used. It will be removed entirely in the Podman 4.0 release.
  • The podman machine start command now prints a message when the VM is successfully started.

... (truncated)

Commits
  • a6493ae Bump to v3.4.1
  • 56a4372 Update release notes for v3.4.1
  • f05e206 Fix test failures from backports
  • 437ec95 system tests: socket activation: clean up
  • 5aa89c8 Checkpoint/Restore test fixes
  • d39e412 Set targetPort to the port value in the kube yaml
  • 7923bfc Test-hang fix: Wait for ready + timeout on connect.
  • c135ff7 Don't include ctr.log if not using file logging
  • 9168db8 Do not add TCP to protocol in generated kube yaml
  • b5dd62f Don't use docker/pkg/archive, use containers/storage/pkg/archive
  • Additional commits viewable in compare view

Dependabot compatibility score

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
build(deps): bump github.com/containers/podman/v3 from 3.3.1 to 3.4.1
8086812 
Bumps [github.com/containers/podman/v3](https://github.com/containers/podman) from 3.3.1 to 3.4.1.
- [Release notes](https://github.com/containers/podman/releases)
- [Changelog](https://github.com/containers/podman/blob/v3.4.1/RELEASE_NOTES.md)
- [Commits](containers/podman@v3.3.1...v3.4.1)

---
updated-dependencies:
- dependency-name: github.com/containers/podman/v3
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <[email protected]>
@dependabot dependabot bot requested review from mrunalp and runcom as code owners October 20, 2021 14:20
@dependabot dependabot bot added the release-note-none Denotes a PR that doesn't merit a release note. label Oct 20, 2021
@openshift-ci openshift-ci bot added dco-signoff: yes Indicates the PR's author has DCO signed all their commits. do-not-merge/release-note-label-needed Indicates that a PR should not merge because it's missing one of the release note labels. labels Oct 20, 2021
@openshift-ci openshift-ci bot removed the do-not-merge/release-note-label-needed Indicates that a PR should not merge because it's missing one of the release note labels. label Oct 20, 2021
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Oct 20, 2021

Hi @dependabot[bot]. Thanks for your PR.

I'm waiting for a cri-o member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@openshift-ci openshift-ci bot added the needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. label Oct 20, 2021
@codecov
Copy link

codecov bot commented Oct 20, 2021

Codecov Report

Merging #5416 (8086812) into main (c22219b) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main    #5416   +/-   ##
=======================================
  Coverage   43.49%   43.49%           
=======================================
  Files         118      118           
  Lines       11786    11786           
=======================================
  Hits         5126     5126           
  Misses       6168     6168           
  Partials      492      492

saschagrunert
saschagrunert approved these changes Oct 20, 2021
View reviewed changes
Copy link
Member

@saschagrunert saschagrunert left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/lgtm
/ok-to-test

@openshift-ci openshift-ci bot added the ok-to-test Indicates a non-member PR verified by an org member that is safe to test. label Oct 20, 2021
@openshift-ci openshift-ci bot added lgtm Indicates that a PR is ready to be merged. and removed needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. labels Oct 20, 2021
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Oct 20, 2021

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: dependabot[bot], saschagrunert

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Oct 20, 2021
@saschagrunert saschagrunert mentioned this pull request Oct 20, 2021
Closed
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Oct 20, 2021

@dependabot[bot]: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name Commit Details Required Rerun command
ci/openshift-jenkins/integration_crun_cgroupv2 8086812 link false /test integration_cgroupv2

Full PR test history. Your PR dashboard.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@openshift-bot
Copy link

openshift-bot commented Oct 20, 2021

/retest-required

Please review the full test history for this PR and help us cut down flakes.

2 similar comments
@openshift-bot
Copy link

openshift-bot commented Oct 20, 2021

/retest-required

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link

openshift-bot commented Oct 20, 2021

/retest-required

Please review the full test history for this PR and help us cut down flakes.

@openshift-merge-robot openshift-merge-robot merged commit 6548676 into main Oct 20, 2021
@dependabot dependabot bot deleted the dependabot/go_modules/github.com/containers/podman/v3-3.4.1 branch October 20, 2021 15:58
@openshift-ci openshift-ci bot mentioned this pull request Oct 21, 2021
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@saschagrunert saschagrunert saschagrunert approved these changes

@mrunalp mrunalp Awaiting requested review from mrunalp mrunalp is a code owner

@runcom runcom Awaiting requested review from runcom

@haircommander haircommander Awaiting requested review from haircommander

@kolyshkin kolyshkin Awaiting requested review from kolyshkin

Assignees

@saschagrunert saschagrunert

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. dco-signoff: yes Indicates the PR's author has DCO signed all their commits. lgtm Indicates that a PR is ready to be merged. ok-to-test Indicates a non-member PR verified by an org member that is safe to test. release-note-none Denotes a PR that doesn't merit a release note.

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

4 participants

@openshift-bot @saschagrunert @openshift-merge-robot