Skip to content
This repository has been archived by the owner on May 30, 2023. It is now read-only.

Upgrade Containerd in main from 1.5.4 to 1.5.5 #1148

Merged
merged 1 commit into from
Aug 13, 2021

Conversation

github-actions[bot]
Copy link

@github-actions github-actions bot commented Jul 30, 2021

@github-actions github-actions bot added the main label Jul 30, 2021
@dongsupark dongsupark requested a review from a team August 6, 2021 07:15
@dongsupark
Copy link
Contributor

CI passed

Copy link
Contributor

@krnowak krnowak left a comment

Choose a reason for hiding this comment

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

Shouldn't we also update COREOS_GO_VERSION="go1.13" to COREOS_GO_VERSION="go1.16"? This is what containerd's go.mod from tag 1.5.5 suggests.

@@ -13,7 +13,7 @@ if [[ ${PV} == *9999 ]]; then
else
MY_PV="${PV/_rc/-rc.}"
EGIT_COMMIT="v${MY_PV}"
CONTAINERD_COMMIT="69a4a55aa42353c71aae40e5bb27a412d8e3149b"
CONTAINERD_COMMIT="d9768bd283183fc51cc587249530adc3fa43ebbb"
Copy link
Contributor

Choose a reason for hiding this comment

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

I don't get where these commits come from. For both 69a4a55aa42353c71aae40e5bb27a412d8e3149b and d9768bd283183fc51cc587249530adc3fa43ebbb I get 404 on github.

Copy link
Contributor

Choose a reason for hiding this comment

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

$ git ls-remote https://github.com/containerd/containerd | tail -n4
69a4a55aa42353c71aae40e5bb27a412d8e3149b        refs/tags/v1.5.4
69107e47a62e1d690afa2b9b1d43f8ece3ff4483        refs/tags/v1.5.4^{}
d9768bd283183fc51cc587249530adc3fa43ebbb        refs/tags/v1.5.5
72cec4be58a9eb6b2910f5d10f1c01ca47d231c0        refs/tags/v1.5.5^{}

they are the hashes of the tags themselves.

Copy link
Contributor

Choose a reason for hiding this comment

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

The commits are generated by git rev-parse VER.

So for v1.5.5, under the containerd repo:

$ git rev-parse v1.5.5
d9768bd283183fc51cc587249530adc3fa43ebbb

$ git show d9768bd283183fc51cc587249530adc3fa43ebbb
tag v1.5.5
Tagger: Derek McGowan <derek@mcg.dev>
Date:   Thu Jul 29 10:03:37 2021 -0700

containerd 1.5.5

...

commit 72cec4be58a9eb6b2910f5d10f1c01ca47d231c0 (tag: v1.5.5)
Merge: 1c13c54c 677fade0
Author: Derek McGowan <derek@mcg.dev>
Date:   Thu Jul 29 10:02:27 2021 -0700

    Merge pull request #5805 from dmcgowan/prepare-1.5.5
    
    [release/1.5] Prepare release notes for v1.5.5

Long story short, d9768bd283183fc51cc587249530adc3fa43ebbb is equivalent to 72cec4be58a9eb6b2910f5d10f1c01ca47d231c0 .

@dongsupark
Copy link
Contributor

Shouldn't we also update COREOS_GO_VERSION="go1.13" to COREOS_GO_VERSION="go1.16"? This is what containerd's go.mod from tag 1.5.5 suggests.

In theory I agree.
We have been using Go 1.13 because of the strange SIGURG issue. Details: #774
Not sure if that issue has been fixed in upstream containerd.

@dongsupark
Copy link
Contributor

I will merge the PR in this week, when there's no objection.

@jepio
Copy link
Contributor

jepio commented Aug 12, 2021

I would like to merge the docker-20 upgrade PR first (#931) and I that will interfere with this PR - I think it'll need to be recreated.

@dongsupark
Copy link
Contributor

I see, go ahead and merge #931 first.

Copy link
Contributor

@dongsupark dongsupark left a comment

Choose a reason for hiding this comment

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

CI passed as well after rebase

@dongsupark dongsupark merged commit 76e4b18 into main Aug 13, 2021
@dongsupark dongsupark deleted the containerd-1.5.5-main branch August 13, 2021 06:49
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants