using docker to deploy on mac #434
Description
running yarn dev-image
mocks-1 | Internal Error: serlo-editor-lti-tool@workspace:.: This package doesn't seem to be present in
your lockfile; run "yarn install" to update the lockfile
mocks-1 | at Xx.getCandidates (/app/.yarn/releases/yarn-4.2.2.cjs:205:8149)
mocks-1 | at Pd.getCandidates (/app/.yarn/releases/yarn-4.2.2.cjs:141:1311)
mocks-1 | at /app/.yarn/releases/yarn-4.2.2.cjs:210:8409
mocks-1 | at Ky (/app/.yarn/releases/yarn-4.2.2.cjs:140:53916)
mocks-1 | at Fe (/app/.yarn/releases/yarn-4.2.2.cjs:210:8389)
mocks-1 | at async Promise.allSettled (index 0)
mocks-1 | at async _c (/app/.yarn/releases/yarn-4.2.2.cjs:140:53244)
mocks-1 | at async /app/.yarn/releases/yarn-4.2.2.cjs:210:9140
mocks-1 | at async Qi.startProgressPromise (/app/.yarn/releases/yarn-4.2.2.cjs:140:137284)
mocks-1 | at async St.resolveEverything (/app/.yarn/releases/yarn-4.2.2.cjs:210:7138)
mocks-1 | Usage Error: Couldn't find the node_modules state file - running an install might help (findPa
ckageLocation)
mocks-1 |
mocks-1 | $ yarn run [--inspect] [--inspect-brk] [-T,--top-level] [-B,--binaries-only] [--require #0] <s
criptName> ...
mocks-1 | [dotenvx@1.44.2] injecting env (0) from .env
mocks-1 |
mocks-1 | node:internal/modules/run_main:123
mocks-1 | triggerUncaughtException(
mocks-1 | ^
mocks-1 | Error:
mocks-1 | You installed esbuild for another platform than the one you're currently using.
mocks-1 | This won't work because esbuild is written with native code and needs to
mocks-1 | install a platform-specific binary executable.
mocks-1 |
mocks-1 | Specifically the "@esbuild/darwin-arm64" package is present but this platform
mocks-1 | needs the "@esbuild/linux-arm64" package instead. People often get into this
mocks-1 | situation by installing esbuild on Windows or macOS and copying "node_modules"
mocks-1 | into a Docker image that runs Linux, or by copying "node_modules" between
mocks-1 | Windows and WSL environments.
mocks-1 |
mocks-1 | If you are installing with npm, you can try not copying the "node_modules"
mocks-1 | directory when you copy the files over, and running "npm ci" or "npm install"
mocks-1 | on the destination platform after the copy. Or you could consider using yarn
mocks-1 | instead of npm which has built-in support for installing a package on multiple
mocks-1 | platforms simultaneously.
mocks-1 |
mocks-1 | If you are installing with yarn, you can try listing both this platform and the
mocks-1 | other platform in your ".yarnrc.yml" file using the "supportedArchitectures"
mocks-1 | feature: https://yarnpkg.com/configuration/yarnrc/#supportedArchitectures
mocks-1 | Keep in mind that this means multiple copies of esbuild will be present.
mocks-1 |
mocks-1 | Another alternative is to use the "esbuild-wasm" package instead, which works
mocks-1 | the same way on all platforms. But it comes with a heavy performance cost and
mocks-1 | can sometimes be 10x slower than the "esbuild" package, so you may also not
mocks-1 | want to do that.
mocks-1 |
mocks-1 | at generateBinPath (/app/node_modules/tsx/node_modules/esbuild/lib/main.js:1743:17)
mocks-1 | at esbuildCommandAndArgs (/app/node_modules/tsx/node_modules/esbuild/lib/main.js:1824:33)
mocks-1 | at ensureServiceIsRunning (/app/node_modules/tsx/node_modules/esbuild/lib/main.js:1981:25)
mocks-1 | at startSyncServiceWorker (/app/node_modules/tsx/node_modules/esbuild/lib/main.js:2188:19)
mocks-1 | at Object.<anonymous> (/app/node_modules/tsx/node_modules/esbuild/lib/main.js:2229:3)
mocks-1 | at Module._compile (node:internal/modules/cjs/loader:1706:14)
mocks-1 | at Object..js (node:internal/modules/cjs/loader:1839:10)
mocks-1 | at Module.load (node:internal/modules/cjs/loader:1441:32)
mocks-1 | at Function._load (node:internal/modules/cjs/loader:1263:12)
mocks-1 | at TracingChannel.traceSync (node:diagnostics_channel:328:14) {
mocks-1 | name: 'TransformError'
mocks-1 | }
mocks-1 |
mocks-1 | Node.js v22.22.0