v1.61.4之后的版本在vercel上持续部署失败

[iparanoid]

📦 部署环境

Vercel

📦 部署模式

服务端模式(lobe-chat-database 镜像)

📌 软件版本

v1.61.4之后的版本

💻 系统环境

macOS

🌐 浏览器

Chrome

🐛 问题描述

这是最新一次部署的结果（已通过github sync fork）

[12:38:35.443] Running build in Washington, D.C., USA (East) – iad1
[12:38:35.555] Cloning github.com/iparanoid/lobe-chat (Branch: main, Commit: 237cc76)
[12:38:37.192] Cloning completed: 1.641s
[12:39:44.452] Restored build cache from previous deployment (FiAXuHsgfRQgEek5THQuLNaUqedY)
[12:39:44.555] Running "vercel build"
[12:39:45.926] Vercel CLI 41.1.4
[12:39:47.022] Running "install" command: bun install...
[12:39:47.066] bun install v1.2.2 (c1708ea6)
[12:39:47.085] Resolving dependencies
[12:40:12.761] Resolved, downloaded and extracted [10034]
[12:40:12.761] warn: incorrect peer dependency "[email protected]"
[12:40:12.761]
[12:40:12.761] warn: incorrect peer dependency "[email protected]"
[12:40:12.761]
[12:40:12.761] warn: incorrect peer dependency "[email protected]"
[12:40:12.761]
[12:40:12.761] warn: incorrect peer dependency "[email protected]"
[12:40:12.761]
[12:40:12.761] warn: incorrect peer dependency "[email protected]"
[12:40:12.761]
[12:40:12.761] warn: incorrect peer dependency "[email protected]"
[12:40:12.761]
[12:40:12.761] warn: incorrect peer dependency "[email protected]"
[12:40:12.761]
[12:40:12.762] warn: incorrect peer dependency "[email protected]"
[12:40:12.762]
[12:40:12.762] warn: incorrect peer dependency "[email protected]"
[12:40:12.762]
[12:40:12.762] warn: incorrect peer dependency "@octokit/[email protected]"
[12:40:12.762]
[12:40:12.762] warn: incorrect peer dependency "[email protected]"
[12:40:12.766]
[12:40:12.767] warn: incorrect peer dependency "[email protected]"
[12:40:12.767]
[12:40:12.767] warn: incorrect peer dependency "[email protected]"
[12:40:12.767]
[12:40:12.767] warn: incorrect peer dependency "[email protected]"
[12:40:12.767]
[12:40:12.767] warn: incorrect peer dependency "[email protected]"
[12:40:12.767]
[12:40:12.767] warn: incorrect peer dependency "[email protected]"
[12:40:12.767]
[12:40:12.767] warn: incorrect peer dependency "[email protected]"
[12:40:12.768]
[12:40:12.768] warn: incorrect peer dependency "[email protected]"
[12:40:18.338] Saved lockfile
[12:40:18.338]
[12:40:18.341] $ husky
[12:40:19.541]
[12:40:19.541] + @types/[email protected]
[12:40:19.541] + [email protected]
[12:40:19.541] + [email protected]
[12:40:19.541] + [email protected]
[12:40:19.541] + @aws-sdk/[email protected]
[12:40:19.541] + @google/[email protected]
[12:40:19.541] + @langchain/[email protected]
[12:40:19.541] + @lobehub/[email protected]
[12:40:19.541] + @serwist/[email protected]
[12:40:19.542] + @tanstack/[email protected]
[12:40:19.542] + @trpc/[email protected]
[12:40:19.542] + @trpc/[email protected]
[12:40:19.542] + @trpc/[email protected]
[12:40:19.542] + @trpc/[email protected]
[12:40:19.542] + [email protected]
[12:40:19.542] + [email protected]
[12:40:19.542] + [email protected]
[12:40:19.542] + [email protected]
[12:40:19.542] + [email protected]
[12:40:19.542] + [email protected]
[12:40:19.542] + [email protected]
[12:40:19.542] + [email protected]
[12:40:19.542] + [email protected]
[12:40:19.542] + [email protected]
[12:40:19.543] + [email protected]
[12:40:19.543] + [email protected]
[12:40:19.543]
[12:40:19.543] 104 packages installed [32.49s]
[12:40:19.587] Detected Next.js version: 15.1.7
[12:40:19.588] Running "NODE_OPTIONS=--max-old-space-size=6144 bun run build"
[12:40:19.594] $ next build
[12:40:23.176] ▲ Next.js 15.1.7
[12:40:23.177] - Experiments (use with caution):
[12:40:23.177] · webpackMemoryOptimizations
[12:40:23.177]
[12:40:23.225] Creating an optimized production build ...
[12:40:23.666] ○ (serwist) The service worker will not be automatically registered, please call 'window.serwist.register()' in 'componentDidMount' or 'useEffect'.
[12:40:23.673] ✓ (serwist) Bundling the service worker script with the URL '/sw.js' and the scope '/'...
[12:44:45.057] error: script "build" was terminated by signal SIGKILL (Forced quit)
[12:44:45.711] Error: Command "NODE_OPTIONS=--max-old-space-size=6144 bun run build" exited with SIGKILL
[12:44:51.305] ▲ Build system report
[12:44:51.305] ▲ To always completely log this report, add VERCEL_BUILD_SYSTEM_REPORT=1 as an Environment Variable to your project.
[12:44:51.305] • At least one "Out of Memory" ("OOM") event was detected during the build.
[12:44:51.305] • This occurs when processes or applications running during the build completely fill up the available memory (RAM) in the build container. When this happens, the build container terminates one of the processes during the build with a SIGKILL signal.
[12:44:51.305] • Read this troubleshooting guide for more information: https://vercel.link/troubleshoot-build-errors

📷 复现步骤

No response

🚦 期望结果

No response

📝 补充信息

No response

[lobehubbot]

👀 @iparanoid

Thank you for raising an issue. We will investigate into the matter and get back to you as soon as possible.
Please make sure you have given us as much context as possible.
非常感谢您提交 issue。我们会尽快调查此事，并尽快回复您。 请确保您已经提供了尽可能多的背景信息。

[dosubot[bot]]

There are a few similar threads related to deployment issues on Vercel that might be helpful:

1. Vercel deployment with database fails with SIGKILL error: This discussion addresses a similar issue where deployments fail with a SIGKILL error. The suggested solution was to add the environment variable VERCEL_FORCE_NO_BUILD_CACHE=1 to help resolve the issue ^[1].

2. Vercel 自动部署经常超时，偶尔才能成功一次，除非手动重新部署: This unsolved discussion mentions frequent timeouts during automatic deployments on Vercel, which might be related to memory issues ^[2].

3. 部署在vercel的lobechat，最近频繁部署失败: Another unsolved discussion about frequent deployment failures on Vercel, which could be relevant to your situation ^[3].

For your specific issue, it seems like the build process is running out of memory, as indicated by the "Out of Memory" event and the SIGKILL signal. You might want to try increasing the memory allocation further or optimizing the build process to reduce memory usage. Additionally, setting the VERCEL_FORCE_NO_BUILD_CACHE=1 environment variable could help if the issue is related to build caching.

To continue talking to Dosu, mention @dosu.

---

^{Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Bug Report | Other}

[bbbugg]

环境变量加一个VERCEL_FORCE_NO_BUILD_CACHE=1

[iparanoid]

已解决，谢谢~