-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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
Cherrypick to v0.37 - update docker client method #2734
Conversation
bobbypage
commented
Nov 18, 2020
•
edited
Loading
edited
- Cherrypick update docker client method update docker client method #2714 to v0.37
- Bump docker to https://github.com/moby/moby/tree/v19.03.8 to match that of k8s 1.19 - https://github.com/kubernetes/kubernetes/blob/release-1.19/go.mod#L39
All (the pull request submitter and all commit authors) CLAs are signed, but one or more commits were authored or co-authored by someone other than the pull request submitter. We need to confirm that all authors are ok with their commits being contributed to this project. Please have them confirm that by leaving a comment that contains only Note to project maintainer: There may be cases where the author cannot leave a comment, or the comment is not properly detected as consent. In those cases, you can manually confirm consent of the commit author(s), and set the ℹ️ Googlers: Go here for more info. |
@JornShen it looks like there's some issues cherrypicking #2714 to v0.37: From CI:
I think the problem is [1] From v0.37
|
/cc @ruiwen-zhao |
It's related to docker client version. Is there problem for us to update the docker version here? |
@dims is there some method for us to use which is same effect as |
@JornShen when you use |
Nevermind, detectDevices was working, initializeNVML was not. Sorry for the noise. |
@dims I meam, are there other method which is same effect as |
@JornShen I looked at this again, I think it should be ok to update docker version. My concern is that when we go to vendor the new cAdvisor patch release back into k/k we want to avoid bumping the docker version since cherrypick should ideally be as small as possible. However, k8s 1.19 seems to be on newer docker already compared to cAdvisor v0.37: From k8s 1.19 go.mod:
https://github.com/kubernetes/kubernetes/blob/release-1.19/go.mod#L39 The PR that made that update was kubernetes/kubernetes#89687. That commit there matches https://github.com/moby/moby/tree/v19.03.8 However cAdvisor v0.37 is using:
https://github.com/google/cadvisor/blob/release-v0.37/go.mod#L17 Since k8s 1.19 is already using newer docker version (that also includes |
go get -u github.com/docker/docker@v1.4.2-0.20200309214505-aa6a9891b09c
update dockerclient.NewClient to dockerclient.NewClientWithOpts and enable client negotiate down to a lower version server version
625b223
to
84e91b2
Compare
All (the pull request submitter and all commit authors) CLAs are signed, but one or more commits were authored or co-authored by someone other than the pull request submitter. We need to confirm that all authors are ok with their commits being contributed to this project. Please have them confirm that by leaving a comment that contains only Note to project maintainer: There may be cases where the author cannot leave a comment, or the comment is not properly detected as consent. In those cases, you can manually confirm consent of the commit author(s), and set the ℹ️ Googlers: Go here for more info. |