did anyone make it work with docker on production?

[bencagri]

hello all, im facing issues with deployment.
according to documentation with node:22-alpine image using same dockerfile, im facing the issue below.

#10 [deps 3/3] RUN npm ci
#10 CACHED
#11 [stage-4 2/3] COPY --from=production-deps /app/node_modules /app/node_modules
#11 CACHED
#12 [build 2/4] COPY --from=deps /app/node_modules /app/node_modules
#12 CACHED
#13 [build 3/4] ADD . .
#13 DONE 0.2s
#14 [build 4/4] RUN node ace build
#14 0.824
#14 0.824 node:internal/modules/run_main:123
#14 0.824     triggerUncaughtException(
#14 0.824     ^
#14 0.825 [Object: null prototype] {
#14 0.825   [Symbol(nodejs.util.inspect.custom)]: [Function: [nodejs.util.inspect.custom]]
#14 0.825 }
#14 0.825
#14 0.825 Node.js v22.16.0
#14 ERROR: process "/bin/sh -c node ace build" did not complete successfully: exit code: 1
------
> [build 4/4] RUN node ace build:
0.824
0.824 node:internal/modules/run_main:123
0.824     triggerUncaughtException(
0.824     ^
0.825 [Object: null prototype] {
0.825   [Symbol(nodejs.util.inspect.custom)]: [Function: [nodejs.util.inspect.custom]]
0.825 }
0.825
0.825 Node.js v22.16.0 

Assuming this is node issue, i have tried with node:20 as well, but no luck.

[RomainLanz]

Hey @bencagri! 👋🏻

What happen when you run node ace build locally?

[bencagri]

hi @RomainLanz it builds on local (mac) but when i try docker-compose up it builds the error above. unfortunately, i couldnt find more detail why it throws the error.

[bencagri]

i think i found the problem, locally it loads swc/core for ARM64-based Mac M1. and locked in package.json
but, destination is AMD64 (x64) Linux processor.

so problem was @swc/core package, additionally it needs @swc/core-linux-x64-musl aligning it in docker solves the problem.

# All deps stage
FROM base AS deps
WORKDIR /app
ADD package.json package-lock.json ./
ENV NODE_ENV=development
RUN npm ci --ignore-scripts=false && npm install --save-dev @swc/[email protected] 👈  this is the fix