-
Notifications
You must be signed in to change notification settings - Fork 39k
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
kubelet cannot show Docker-CE version correctly #54039
Comments
/sig node |
…sing Automatic merge from submit-queue (batch tested with PRs 54040, 52503). If you want to cherry-pick this change to another branch, please follow the instructions <a href="https://github.com/kubernetes/community/blob/master/contributors/devel/cherry-picks.md">here</a>. falls back to parse Docker runtime version as generic if not semver **What this PR does / why we need it**: **Which issue this PR fixes** *(optional, in `fixes #<issue number>(, fixes #<issue_number>, ...)` format, will close that issue when PR gets merged)*: fixes #54039 **Special notes for your reviewer**: /assign @tallclair @vishh **Release note**: ```release-note falls back to parse Docker runtime version as generic if not semver ```
I have same problem in v1.8.3+coreos.0. |
@jpbetz is patch release manager for v1.8 |
I have same problem in v1.8.4 too,how to fix it? |
@xyalan @Bobi-zhou Sorry for the delay. I've already cherry-picked the fix to release-1.8. Please refer to #56945. The fix should be available in v1.8.6. For current already-released v1.8 version, please cherry-pick the fix manually if you really need it and re-compile And v1.9 is coming out soon, targeted on Dec 13. You can wait for this new version, which has already included the fix. |
Is this a BUG REPORT or FEATURE REQUEST?:
/kind bug
What happened:
What you expected to happen:
Should show a version intead of
docker://Unknown
, which is confusing.How to reproduce it (as minimally and precisely as possible):
As above
Anything else we need to know?:
Environment:
kubectl version
):The text was updated successfully, but these errors were encountered: