-
Notifications
You must be signed in to change notification settings - Fork 467
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
Memory check for cscli dashboard setup #1513
Conversation
…s flag cause they already provided it
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
minor suggestion, overall lgtm 👍
Since checking the RAM is not required to get the container up and running we can change this to a warn level
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm
If total memory < 1GB and force-yes is not provided the user can answer Y/n to continue running the Metabase container if the force-yes flag is provided it will just warn the user that Metabase container requires 1-2GB
Please note the current calculation of memory is set to 1GB as per issue, however, in crowdsec documentation it states 1-2GB
EDIT: The free system memory function was acting a bit strange on my VM it listed only 57MB free instead of 570MB so for the first implementation I thought total memory can be an improvement.
I have done some more testing and the free memory is correct for my VM after system allocation. I can update this PR with the check for free system memory check as well, however, I will wait for feedback.
#826