Dokploy 部署问题

[SpeedupMaster]

今天dokploy自动部署报错：

#12 3.724  ✓ (serwist) Bundling the service worker script with the URL '/sw.js' and the scope '/'...
#12 529.5 
#12 529.5 <--- Last few GCs --->
#12 529.5 
#12 529.5 [25:0x32936d0]   523065 ms: Mark-sweep 3451.3 (4104.5) -> 3451.3 (4097.5) MB, 2233.8 / 0.0 ms  (average mu = 0.210, current mu = 0.000) allocation failure; GC in old space requested
#12 529.5 [25:0x32936d0]   525718 ms: Mark-sweep (reduce) 3451.3 (4097.5) -> 3451.3 (4050.5) MB, 2652.1 / 0.0 ms  (average mu = 0.118, current mu = 0.000) last resort; GC in old space requested
#12 529.5 
#12 529.5 
#12 529.5 <--- JS stacktrace --->
#12 529.5 
#12 529.5 FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memory
#12 529.5  1: 0xac22d8 node::Abort() [node]
#12 529.5  2: 0x9ad387  [node]
#12 529.5  3: 0xcccdd0 v8::Utils::ReportOOMFailure(v8::internal::Isolate*, char const*, bool) [node]
#12 529.5  4: 0xccd1ab v8::internal::V8::FatalProcessOutOfMemory(v8::internal::Isolate*, char const*, bool) [node]
#12 529.5  5: 0xec4a45  [node]
#12 529.5  6: 0xec4b31  [node]
#12 529.5  7: 0xed9e62 v8::internal::Heap::PerformGarbageCollection(v8::internal::GarbageCollector, v8::internal::GarbageCollectionReason, char const*, v8::GCCallbackFlags) [node]
#12 529.5  8: 0xedaa2a v8::internal::Heap::CollectGarbage(v8::internal::AllocationSpace, v8::internal::GarbageCollectionReason, v8::GCCallbackFlags) [node]
#12 529.5  9: 0xedd1de v8::internal::Heap::CollectAllAvailableGarbage(v8::internal::GarbageCollectionReason) [node]
#12 529.5 10: 0xeb627b v8::internal::HeapAllocator::AllocateRawWithRetryOrFailSlowPath(int, v8::internal::AllocationType, v8::internal::AllocationOrigin, v8::internal::AllocationAlignment) [node]
#12 529.5 11: 0xe9490b v8::internal::Factory::AllocateRaw(int, v8::internal::AllocationType, v8::internal::AllocationAlignment) [node]
#12 529.5 12: 0xe8a65c v8::internal::FactoryBase<v8::internal::Factory>::NewFixedArrayWithMap(v8::internal::Handle<v8::internal::Map>, int, v8::internal::AllocationType) [node]
#12 529.5 13: 0x11751b7 v8::internal::MaybeHandle<v8::internal::OrderedHashMap> v8::internal::OrderedHashTable<v8::internal::OrderedHashMap, 2>::Allocate<v8::internal::Isolate>(v8::internal::Isolate*, int, v8::internal::AllocationType) [node]
#12 529.5 14: 0x117526c v8::internal::MaybeHandle<v8::internal::OrderedHashMap> v8::internal::OrderedHashTable<v8::internal::OrderedHashMap, 2>::Rehash<v8::internal::Isolate>(v8::internal::Isolate*, v8::internal::Handle<v8::internal::OrderedHashMap>, int) [node]
#12 529.5 15: 0x1296f42 v8::internal::Runtime_MapGrow(int, unsigned long*, v8::internal::Isolate*) [node]
#12 529.5 16: 0x17087b9  [node]
#12 553.9 Aborted (core dumped)
#12 553.9  ELIFECYCLE  Command failed with exit code 134.
#12 ERROR: executor failed running [/bin/bash -ol pipefail -c pnpm run build]: exit code: 134
------
 > [stage-0  8/10] RUN --mount=type=cache,id=SaWuB9sGL58-next/cache,target=/app/.next/cache --mount=type=cache,id=SaWuB9sGL58-node_modules/cache,target=/app/node_modules/.cache pnpm run build:
529.5  9: 0xedd1de v8::internal::Heap::CollectAllAvailableGarbage(v8::internal::GarbageCollectionReason) [node]
529.5 10: 0xeb627b v8::internal::HeapAllocator::AllocateRawWithRetryOrFailSlowPath(int, v8::internal::AllocationType, v8::internal::AllocationOrigin, v8::internal::AllocationAlignment) [node]
529.5 11: 0xe9490b v8::internal::Factory::AllocateRaw(int, v8::internal::AllocationType, v8::internal::AllocationAlignment) [node]
529.5 12: 0xe8a65c v8::internal::FactoryBase<v8::internal::Factory>::NewFixedArrayWithMap(v8::internal::Handle<v8::internal::Map>, int, v8::internal::AllocationType) [node]
529.5 13: 0x11751b7 v8::internal::MaybeHandle<v8::internal::OrderedHashMap> v8::internal::OrderedHashTable<v8::internal::OrderedHashMap, 2>::Allocate<v8::internal::Isolate>(v8::internal::Isolate*, int, v8::internal::AllocationType) [node]
529.5 14: 0x117526c v8::internal::MaybeHandle<v8::internal::OrderedHashMap> v8::internal::OrderedHashTable<v8::internal::OrderedHashMap, 2>::Rehash<v8::internal::Isolate>(v8::internal::Isolate*, v8::internal::Handle<v8::internal::OrderedHashMap>, int) [node]
529.5 15: 0x1296f42 v8::internal::Runtime_MapGrow(int, unsigned long*, v8::internal::Isolate*) [node]
529.5 16: 0x17087b9  [node]
553.9 Aborted (core dumped)
553.9  ELIFECYCLE  Command failed with exit code 134.

问了下GPT，添加了 NIXPACKS_BUILD_CMD="NODE_OPTIONS='--max-old-space-size=8192' pnpm run build" 这个环境变量成功部署，不过内存占用很大，正常使用下内存占用6.5G左右，部署过程中占用可以到14G以上。不知道是不是和设置的 max-old-space-size=8192 有关。部署v1.40.2版本出现，v1.39.3版本及之前没遇到过这个问题。

[arvinxx]

这个是内存溢出的问题，目前构建占用内存一直很大，所以不建议生产上加 --max-old-space-size=8192，这种做法比较好的还是构建用一台机器，构建完的部署用另外一台机器。构建和运行分离开来。

当然另外一种做法降低构建内存占用的是关掉next 构建后的 ts 类型检测，据说就不会遇到这个问题了

[SpeedupMaster]

我试试关掉类型检测。本来还打算换个10G内存的VPS的，看样子还是得继续用这台大内存的VPS...