github-starred/open-webui
2
0
Fork 0
mirror of https://github.com/open-webui/open-webui.git synced 2026-05-07 03:18:23 -05:00
Code Issues 1.3k Packages Projects Releases 126 Wiki Activity

[PR #5639] [CLOSED] build: Allow node to use more RAM during build #8518

New Issue
Closed
opened 2025-11-11 17:58:35 -06:00 by GiteaMirror · 0 comments
GiteaMirror commented 2025-11-11 17:58:35 -06:00
Owner
Copy Link

📋 Pull Request Information

Original PR: https://github.com/open-webui/open-webui/pull/5639
Author: @sebdanielsson
Created: 9/23/2024
Status: ❌ Closed

Base: dev ← Head: fix-build-error

📝 Commits (1)

  • 7e1931b Allow node to use more RAM during build

📊 Changes

1 file changed (+1 additions, -0 deletions)

View changed files

📝 Dockerfile (+1 -0)

📄 Description

Changelog Entry

Description

Allow node to use more RAM during the npm run build step. I'm developing on an M1 Macbook Air with 16 GB of RAM. I've configured Orbstack which I use instead of Docker Desktop to let Docker use 12 GB of RAM. When building the Dockerfile Node only use around 2096 MB of RAM during the npm build step. After some troubleshooting I increased the limit to 4096 MB and the build completed successfully.

Not sure how this value is calculated or if it's fixed for everyone but you can check it with:

docker run --rm node:21-alpine3.19 node -e "console.log(v8.getHeapStatistics().heap_size_limit / 1024 / 1024 + ' MB');"

Changed

  • Increase the amount of RAM node can use during build

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/open-webui/open-webui/pull/5639 **Author:** [@sebdanielsson](https://github.com/sebdanielsson) **Created:** 9/23/2024 **Status:** ❌ Closed **Base:** `dev` ← **Head:** `fix-build-error` --- ### 📝 Commits (1) - [`7e1931b`](https://github.com/open-webui/open-webui/commit/7e1931b440cd751e8a122a9ca16ec1a5ef24b37a) Allow node to use more RAM during build ### 📊 Changes **1 file changed** (+1 additions, -0 deletions) <details> <summary>View changed files</summary> 📝 `Dockerfile` (+1 -0) </details> ### 📄 Description # Changelog Entry ### Description Allow node to use more RAM during the npm run build step. I'm developing on an M1 Macbook Air with 16 GB of RAM. I've configured Orbstack which I use instead of Docker Desktop to let Docker use 12 GB of RAM. When building the Dockerfile Node only use around 2096 MB of RAM during the npm build step. After some troubleshooting I increased the limit to 4096 MB and the build completed successfully. Not sure how this value is calculated or if it's fixed for everyone but you can check it with: ```sh docker run --rm node:21-alpine3.19 node -e "console.log(v8.getHeapStatistics().heap_size_limit / 1024 / 1024 + ' MB');" ``` ### Changed - Increase the amount of RAM node can use during build --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
GiteaMirror added the pull-request label 2025-11-11 17:58:35 -06:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
confirmed
confirmed issue
core
documentation
enhancement
good first issue
help wanted
non-core
pull-request
Mirrored from GitHub Pull Request
 python
question
testing wanted
No Label pull-request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/open-webui#8518
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?