-
Notifications
You must be signed in to change notification settings - Fork 7
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
add cpu and memory constraints #110
add cpu and memory constraints #110
Conversation
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.
Cool feature to have, left some comments.
README.md
Outdated
@@ -79,7 +79,9 @@ curl -X POST http://localhost:4434/createservice \ | |||
"type": "postgres", | |||
"name": "localtest", | |||
"username": "spinup", | |||
"password": "spinup" | |||
"password": "spinup", | |||
"memory": "6000", //In Megabytes |
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.
So this is 6GB, correct? was curious if someone is running it on say...a system with < 6GB, what would docker do in that case?
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.
right,will have to add error messages for edge cases like this
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.
Yeah, was just curious anyway. Since this is just an example and users can adjust based on their system...it should likely be fine, plus creating the container will probably fail
760c3f4
to
b276190
Compare
This PR adds the feature to restrict memory and CPU resource constraints and partially addresses #22