-
Notifications
You must be signed in to change notification settings - Fork 126
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
Update README.md about memory allocation to Docker #30
Conversation
Welcome @riita10069! |
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.
thanks
README.md
Outdated
@@ -53,6 +53,9 @@ make docker_build_and_up | |||
|
|||
Then, you can access the simulator with http://localhost:3000 | |||
|
|||
Note: 4GB of memory should be allocated to Docker. |
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.
We haven't exactly figured out the cause. This problem may occur only in docker for mac. (I mean it may not always require 4GB momory)
So, lMO it is better to change the wording to something a little more ambiguous.
like:
Note: Insufficient memory allocation sometimes causes problems in building the image.
Please allocate enough memory 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.
4GB sounds like a lot. What is consuming that? the frontend or the backend?
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.
Failing to build an Image.
I had a problem with 2GB memory allocation.
With 4GB, it did not happen.
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.
@riita10069 can you change this PR description to like Fixes #29
Because GitHub automatically close the issue after this PR is merged
https://docs.github.com/en/issues/tracking-your-work-with-issues/linking-a-pull-request-to-an-issue#linking-a-pull-request-to-an-issue-using-a-keyword
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.
I've been investigating for a while, but I couldn't find any solution to this issue.
It seems that there are cases where something uses a lot of memory during the build process of nodejs. In some cases, such problems can be solved by introducing NODE_OPTIONS="–-max_old_space_size=XXX"
, but it did not solve our problem.
So, I'd like to accept this change -- The simplest solution is to allocate more memory.
And, when we provide the image for the simulator (#19), users will not have to build the image themselves. So fewer users will face this problem.
/lgtm
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: alculquicondor, riita10069, sanposhiho The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Fixes #29
/kind bug