Skip to content

vendor: github.com/containerd/containerd v1.7.8#2114

Closed
thaJeztah wants to merge 5 commits intodocker:masterfrom
thaJeztah:update_containerd
Closed

vendor: github.com/containerd/containerd v1.7.8#2114
thaJeztah wants to merge 5 commits intodocker:masterfrom
thaJeztah:update_containerd

Conversation

@thaJeztah
Copy link
Copy Markdown
Member

vendor: golang.org/x/tools v0.10.0

full diff: golang/tools@v0.7.0...v0.10.0

vendor: google.golang.org/protobuf v1.31.0

vendor: golang.org/x/oauth2 v0.10.0

full diff: golang/oauth2@v0.5.0...v0.10.0

vendor: google.golang.org/grpc v1.58.3

vendor: github.com/containerd/containerd v1.7.8

full diff: containerd/containerd@v1.7.7...v1.7.8

full diff: golang/tools@v0.7.0...v0.10.0

Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
full diff: golang/oauth2@v0.5.0...v0.10.0

Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
full diff: containerd/containerd@v1.7.7...v1.7.8

Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
@crazy-max
Copy link
Copy Markdown
Member

I think we prefer to make containerd or other updates (not directly tight to buildx) through a BuildKit update like #2096 so we instead infer these updates. Same as updating gRPC in BuildKit so we infer this update through containerd like moby/buildkit#4393.

We could update BuildKit here after moby/buildkit#4383 is merged so we also bring docker 25 update?

@thaJeztah
Copy link
Copy Markdown
Member Author

Yes, I had this as part of my branch to get the v25 update, and thought I'd open these already in advance

@thaJeztah
Copy link
Copy Markdown
Member Author

updated my other branch to include buildkit updates, and pushed it as a PR; #2118

@thaJeztah thaJeztah deleted the update_containerd branch November 15, 2023 15:47
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants