-
Notifications
You must be signed in to change notification settings - Fork 703
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
MongoDB upgrade #3918
Comments
Hi @mtcolman , we will take this mongo upgrade in LitmusChaos 3.0. Thanks for reminding this. |
The base image of |
FYI -
|
Mongo has been upgraded as part of 3.0 GA: litmuschaos/test-tools@8b624a7 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Question
Hi, apologies if this should have been a bug report or feature request.
As per the issue I've raised here: litmuschaos/test-tools#336,
The image
litmuschaos/mongo:4.2.8
is being used in litmus 3.0.0 (e.g. here: https://github.com/litmuschaos/litmus/blob/master/mkdocs/docs/3.0.0-beta4/litmus-3.0.0-beta4.yaml#L823), it is very old (2 years) and comes from (I believe) here.It has a lot of vulnerabilities:
It uses upstream
mongo:4.2.8
and the latest version (11 days old) ismongo:6.0.4
.What I'd like to know is how the upgrade should be performed/correlated given it is cross-repo and if there is a reason why such an old image is still in use etc? And how can we go about getting this resolved?
Thanks!
The text was updated successfully, but these errors were encountered: