-
Notifications
You must be signed in to change notification settings - Fork 4.7k
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
Newer versions of docker do not follow Semantic Versioning #3559
Conversation
Hi @brdude. Thanks for your PR. I'm waiting for a kubernetes member to verify that this patch is reasonable to test. If it is, they should reply with 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/test-infra repository. I understand the commands that are listed here. |
/ok-to-test |
/assign @chrislovecnm |
Good point! One option long term might be write a more relaxed parser for parsing the docker version, as I think it is probably still "semver compatible" even if it doesn't follow the semver rules. (One simple option might be to simply to strip any leading zeroes). But I like what you've done here! /lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: justinsb The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these OWNERS Files:
You can indicate your approval by writing |
/test all [submit-queue is verifying that this PR is safe to merge] |
Automatic merge from submit-queue. |
Newer versions of docker do not follow Semantic Versioning. When selecting docker version 17.03.2 the following error occurs.
main.go:141] got error running nodeup (will retry in 30s): error building loader: error parsing docker version "17.03.2" as semver: Minor number must not contain leading zeroes 03