Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
[FEATURE]: Allow setting resource requests on the container module
See original GitHub issueFeature Request
Background / Motivation
Currently you can only set resource limits on container modules. But some users have requested setting resource requests as well.
Feels like this is generic enough to belong on the container module. For example docker swarm has a resource reservations field.
What should the user be able to do?
Set resource requests on a container module, similar to resource limits.
Why do they want to do this? What problem does it solve?
From community Slack:
For doing things like running tests in CI with garden, we might want to make sure we have the correct reservations
Suggested Implementation(s)
Same as for resource limits.
Issue Analytics
- State:
- Created 4 years ago
- Reactions:3
- Comments:5 (1 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Can we also be able to change the requests on tests/tasks as well?
We have some giant webpack builds and want to make sure they complete in a reasonable amount of time and don’t run out of memory.
Also mentioned to bump the default to 100m.