Increase and centralize build memory limits #3211
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Follow-up to jupyterhub#3204, which failed because it removed the limit, which caused it to be lower than the request. All the reasons given in that PR still apply. Here I bump up the limit enough until the super popular https://github.com/jupyterlab/jupyterlab-demo is able to build. It's not a functionally super complex environment.yml, and even with simplifications in jupyterlab/jupyterlab-demo#147, it fails to build without the memory increase limit. As mentioned in the other PR, jupyterhub/repo2docker#1402 will get rid of this kind of limit anyway, so it's ok to raise this.
|
@yuvipanda Regarding GESIS, the configuration is still in https://github.com/gesiscss/orc2/blob/59a67b86fa4325455041332596532c6afcbcfd8e/helm/gesis-config/production.yaml. I'm trying to move it to this repository. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Follow-up to #3204, which failed because it removed the limit, which caused it to be lower than the request. All the reasons given in that PR still apply.
Here I bump up the limit enough until the super popular https://github.com/jupyterlab/jupyterlab-demo is able to build. It's not a functionally super complex environment.yml, and even with simplifications in jupyterlab/jupyterlab-demo#147, it fails to build without the memory increase limit. As mentioned in the other PR, jupyterhub/repo2docker#1402 will get rid of this kind of limit anyway, so it's ok to raise this.