-
Notifications
You must be signed in to change notification settings - Fork 2.4k
Default image on gcr.io downloads a 3 year old image #3363
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
Comments
@bobbypage, can you take a look, please? |
It is a bit confusing, but there was issue that Not to mention, it was updated since this issue 😅 |
Agree with you, having a 'latest' tag only makes sense if one actually updates it. If regularly updating the 'latest' tag is still no option I would guess removing it would probably be the way to go. I am curious how many projects just use 'latest' and are not aware that they are using a pretty old version of cadvisor. |
Don't be the unicorn and do some weird other thing of an otherwise common used principle, please fix this! |
The Update: This may have been a one-off and not a change of process/policy as v0.50.0 has not (yet) received the same treatment. |
new docker images is now in registry, seems to be solved |
The Also, why aren't there any new releases on github after |
gcr.io/cadvisor/cadvisor pulls a 3 year old version of cadvisor (v0.38.6).
Expected behaviour: Pull the latest version (v0.47.2).
Actual behaviour: Pulls version v0.38.6
The 'latest' tag seems to not have been updated since December of 2020. This results in downstream projects to have to update the version of the docker images manually. See the following commit as an example: eth-educators/eth-docker@6c1ec39
The text was updated successfully, but these errors were encountered: