10 months ago
ERROR: process "/bin/bash -ol pipefail -c yarn install --frozen-lockfile" did not complete successfully: exit code: 1
0 Replies
10 months ago
Mind sending your build logs?
10 months ago
It's a bookmarklet that'll help you download your build logs so I can see them
10 ERROR: process "/bin/bash -ol pipefail -c yarn install --frozen-lockfile" did not complete successfully: exit code: 1
> [stage-0 6/8] RUN --mount=type=cache,id=s/2f07ba9a-d3d2-42ef-8935-ae4e4f5d0a36-/usr/local/share/cache/yarn/v6,target=/usr/local/share/.cache/yarn/v6 yarn install --frozen-lockfile:
0.495 at Parser.unexpected (/nix/store/7sdnkhvwz3imx4qnf6ifbjwba13r61hc-yarn/lib/cli.js:64026:11)
0.495 at Parser.parse (/nix/store/7sdnkhvwz3imx4qnf6ifbjwba13r61hc-yarn/lib/cli.js:64154:16)
0.495 at Parser.parse (/nix/store/7sdnkhvwz3imx4qnf6ifbjwba13r61hc-yarn/lib/cli.js:64131:26)
0.495 at parse (/nix/store/7sdnkhvwz3imx4qnf6ifbjwba13r61hc-yarn/lib/cli.js:64231:21)
0.495 at module.exports.exports.default (/nix/store/7sdnkhvwz3imx4qnf6ifbjwba13r61hc-yarn/lib/cli.js:63793:96)
0.495 at Function. (/nix/store/7sdnkhvwz3imx4qnf6ifbjwba13r61hc-yarn/lib/cli.js:3068:63)
0.495 at Generator.next ()
0.495 at step (/nix/store/7sdnkhvwz3imx4qnf6ifbjwba13r61hc-yarn/lib/cli.js:310:30)
0.495 at /nix/store/7sdnkhvwz3imx4qnf6ifbjwba13r61hc-yarn/lib/cli.js:321:13
0.495 info Visit https://yarnpkg.com/en/docs/cli/install for documentation about this command.
Dockerfile:20
18 | ENV NIXPACKSPATH=/app/nodemodules/.bin:$NIXPACKS_PATH
19 | COPY . /app/.
20 | >>> RUN --mount=type=cache,id=s/2f07ba9a-d3d2-42ef-8935-ae4e4f5d0a36-/usr/local/share/cache/yarn/v6,target=/usr/local/share/.cache/yarn/v6 yarn install --frozen-lockfile
21 |
22 | # build phase
ERROR: failed to solve: process "/bin/bash -ol pipefail -c yarn install --frozen-lockfile" did not complete successfully: exit code: 1
Error: Docker build failed
10 months ago
alternatively, just do ctrl+k or cmd+k and then click Download Build Logs (while having your deployment open)
10 months ago
damn, that's weird
10 months ago
oh dope, what was the issue?
node:internal/modules/cjs/loader:1460
return process.dlopen(module, path.toNamespacedPath(filename));
^
Error: /app/node_modules/canvas/build/Release/canvas.node: invalid ELF header
at Module._extensions..node (node:internal/modules/cjs/loader:1460:18)
at Module.load (node:internal/modules/cjs/loader:1203:32)
at Module._load (node:internal/modules/cjs/loader:1019:12)
at Module.require (node:internal/modules/cjs/loader:1231:19)
at require (node:internal/modules/helpers:177:18)
at Object. (/app/node_modules/canvas/lib/bindings.js:3:18)
at Module._compile (node:internal/modules/cjs/loader:1364:14)
at Module._extensions..js (node:internal/modules/cjs/loader:1422:10)
at Module.load (node:internal/modules/cjs/loader:1203:32)
at Module._load (node:internal/modules/cjs/loader:1019:12) {
code: 'ERR_DLOPEN_FAILED'
}
Node.js v18.20.210 months ago
the invalid ELF error happens when the binary of the package doesn't fit the operating system it's running on
Usually when you install packages they install the correct type for the operating system but if you're committing node_modules along with your code then it won't have a chance to download the correct version
so make sure you're not committing node_modules and delete it if you have been so it's removed from Github
10 months ago
sorry for taking so long to respond, i was making some food