Skip to content
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.

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

[release/1.7] bump github.com/containerd/continuity from 0.4.2 to 0.4.4 #11216

Merged
merged 3 commits into from
Jan 2, 2025

Conversation

sondavidb
Copy link
Contributor

@sondavidb sondavidb commented Jan 2, 2025

Cherry-picked from #9410 and #10901 and #11024

This fix includes a bug in the CRI plugin where calling fs.CopyDir() would fail on layers without xattr support (ref: containerd/continuity#244).

Aside from fixing issues on older filesystems, any FUSE-based filesystems (e.g. SOCI snapshotter's snapshots) experience notable performance benefits without having to use expensive xattr operations. Thus, it would be helpful to have this bugfix backported to 1.7.

As part of the upgrade protobuf was bumped from v1.33.0 to v1.35.2. This was squashed from multiple commits with the final one being the one from #11024

ktock and others added 3 commits January 1, 2025 20:39
Signed-off-by: Kohei Tokunaga <[email protected]>
(cherry picked from commit 6da0152)
Signed-off-by: David Son <[email protected]>
Bumps google.golang.org/protobuf from 1.33.0 to 1.35.2.

---
updated-dependencies:
- dependency-name: google.golang.org/protobuf
  dependency-type: direct:production
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <[email protected]>
(cherry picked from commit dd2d891)
Signed-off-by: David Son <[email protected]>
Bumps [github.com/containerd/continuity](https://github.com/containerd/continuity) from 0.4.3 to 0.4.4.
- [Release notes](https://github.com/containerd/continuity/releases)
- [Commits](containerd/continuity@v0.4.3...v0.4.4)

---
updated-dependencies:
- dependency-name: github.com/containerd/continuity
  dependency-type: direct:production
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <[email protected]>
(cherry picked from commit 1814910)
Signed-off-by: David Son <[email protected]>
@k8s-ci-robot
Copy link

Hi @sondavidb. Thanks for your PR.

I'm waiting for a containerd 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.

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-sigs/prow repository.

@dosubot dosubot bot added the dependencies Pull requests that update a dependency file label Jan 2, 2025
@sondavidb
Copy link
Contributor Author

sondavidb commented Jan 2, 2025

Sorry I accidentally deleted the branch while doing some rebasing shenanigans and it didn't let me reopen the old PR so I opened a new one 😓 guess it's better to have a clean slate anyway since the last PR was a mess...

cc @dmcgowan since you approved the previous PR. Apologies for the trouble again

@estesp
Copy link
Member

estesp commented Jan 2, 2025

/ok-to-test

@dmcgowan dmcgowan merged commit 54eec10 into containerd:release/1.7 Jan 2, 2025
109 of 111 checks passed
@sondavidb sondavidb deleted the 1.7-continuity-update branch January 8, 2025 23:58
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Pull requests that update a dependency file ok-to-test size/XXL
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants