Closed akamil-etsy closed 8 months ago
Hi, can you try deleting yarn.lock and removing it from the dockerfile COPY command?
same error.
i removed yarn.lock file and removed it from dockerfile COPY command, and ran docker build with --no-cache
option
separately also tried the same after commenting out the lines added in PR16.
also restarted the mac as it was low on memory but it didn't help
it works fine from windows or linux vm but not from my Mac, I guess I can try building some dummy quasar app from their official site and see if it works
Quasar released a new cli maybe it fixed your build problem? https://www.npmjs.com/package/@quasar/cli Does the built dockerimage work?
Hello, same problem here, how did you solved the problem @akamil-etsy (I you ever solved it 😂)? This is the output of docker build
DEPRECATED: The legacy builder is deprecated and will be removed in a future release.
Install the buildx component to build images with BuildKit:
https://docs.docker.com/go/buildx/
Sending build context to Docker daemon 2.482MB
Step 1/17 : ARG PUBLIC_PATH=/
Step 2/17 : FROM --platform=linux/amd64 node:18-alpine as builder
---> 3bf7cda95541
Step 3/17 : ARG PUBLIC_PATH
---> Using cache
---> 75903852d501
Step 4/17 : WORKDIR /app
---> Using cache
---> 37e342d3ac7a
Step 5/17 : RUN apk add --no-cache --virtual .gyp g++ make py3-pip
---> Using cache
---> 19846d5737ec
Step 6/17 : RUN yarn global add @quasar/cli
---> Using cache
---> 03f1e3c10fcd
Step 7/17 : COPY package.json ./
---> 97d6c1f3579d
Step 8/17 : RUN yarn install
---> Running in 0844fa825a9b
yarn install v1.22.19
info No lockfile found.
[1/5] Validating package.json...
[2/5] Resolving packages...
warning vue-instantsearch > instantsearch.js > hogan.js > mkdirp@0.3.0: Legacy versions of mkdirp are no longer supported. Please update to mkdirp 1.x. (Note that the API surface has changed to use Promises in 1.x.)
warning @quasar/app-webpack > webpack-chain@6.5.1: Package no longer supported. Contact Support at https://www.npmjs.com/support for more info.
warning @quasar/app-webpack > fork-ts-checker-webpack-plugin > glob@7.2.3: Glob versions prior to v9 are no longer supported
warning @quasar/app-webpack > archiver > archiver-utils > glob@7.2.3: Glob versions prior to v9 are no longer supported
warning @quasar/app-webpack > archiver > zip-stream > archiver-utils > glob@7.2.3: Glob versions prior to v9 are no longer supported
warning @quasar/app-webpack > fork-ts-checker-webpack-plugin > memfs@3.6.0: this will be v4
warning @quasar/app-webpack > webpack-dev-server > rimraf@3.0.2: Rimraf versions prior to v4 are no longer supported
warning @quasar/app-webpack > webpack-dev-server > rimraf > glob@7.2.3: Glob versions prior to v9 are no longer supported
warning @quasar/app-webpack > webpack-dev-server > webpack-dev-middleware > memfs@3.6.0: this will be v4
warning @quasar/app-webpack > fork-ts-checker-webpack-plugin > glob > inflight@1.0.6: This module is not supported, and leaks memory. Do not use it. Check out lru-cache if you want a good and tested way to coalesce async requests by a key value, which is much more comprehensive and powerful.
warning @quasar/app-webpack > cssnano > cssnano-preset-default > postcss-svgo > svgo > stable@0.1.8: Modern JS already guarantees Array#sort() is a stable sort, so this library is deprecated. See the compatibility table on MDN: https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Array/sort#browser_compatibility
warning electron-installer-zip > archiver > glob@6.0.4: Glob versions prior to v9 are no longer supported
warning electron-installer-zip > fs-extra > rimraf@2.7.1: Rimraf versions prior to v4 are no longer supported
warning electron-installer-zip > archiver > archiver-utils > glob@6.0.4: Glob versions prior to v9 are no longer supported
warning electron-installer-zip > archiver > glob > inflight@1.0.6: This module is not supported, and leaks memory. Do not use it. Check out lru-cache if you want a good and tested way to coalesce async requests by a key value, which is much more comprehensive and powerful.
warning electron-installer-zip > fs-extra > rimraf > glob@7.2.3: Glob versions prior to v9 are no longer supported
warning electron-installer-zip > zip-folder > archiver > glob@3.2.11: Glob versions prior to v9 are no longer supported
warning electron-installer-zip > zip-folder > archiver > glob > minimatch@0.3.0: Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue
warning electron-packager@17.1.2: Please use @electron/packager moving forward. There is no API change, just a package name change
warning electron-packager > @electron/asar > glob@7.2.3: Glob versions prior to v9 are no longer supported
warning eslint > file-entry-cache > flat-cache > rimraf@3.0.2: Rimraf versions prior to v4 are no longer supported
warning eslint > @humanwhocodes/config-array@0.11.14: Use @eslint/config-array instead
warning eslint > @humanwhocodes/config-array > @humanwhocodes/object-schema@2.0.3: Use @eslint/object-schema instead
[3/5] Fetching packages...
[4/5] Linking dependencies...
warning " > monaco-editor-webpack-plugin@7.1.0" has unmet peer dependency "webpack@^4.5.0 || 5.x".
warning " > vue-instantsearch@4.15.0" has unmet peer dependency "algoliasearch@>= 3.32.0 < 5".
warning "vue-instantsearch > instantsearch.js@4.66.1" has unmet peer dependency "algoliasearch@>= 3.1 < 6".
warning "vue-instantsearch > instantsearch.js > algoliasearch-helper@3.17.0" has unmet peer dependency "algoliasearch@>= 3.1 < 6".
warning " > @babel/eslint-parser@7.24.1" has unmet peer dependency "@babel/core@^7.11.0".
warning "@typescript-eslint/eslint-plugin > ts-api-utils@1.3.0" has unmet peer dependency "typescript@>=4.2.0".
warning "@vue/devtools > @vue/devtools-electron > @vue/devtools-core > vite-hot-client@0.2.3" has unmet peer dependency "vite@^2.6.0 || ^3.0.0 || ^4.0.0 || ^5.0.0-0".
[5/5] Building fresh packages...
success Saved lockfile.
Done in 148.84s.
---> Removed intermediate container 0844fa825a9b
---> c423b1bcef26
Step 9/17 : COPY . .
---> 4726b5e088ec
Step 10/17 : RUN quasar build
---> Running in 3157b0a90fe2
.d88888b.
d88P" "Y88b
888 888
888 888 888 888 8888b. .d8888b 8888b. 888d888
888 888 888 888 "88b 88K "88b 888P"
888 Y8b 888 888 888 .d888888 "Y8888b. .d888888 888
Y88b.Y8b88P Y88b 888 888 888 X88 888 888 888
"Y888888" "Y88888 "Y888888 88888P' "Y888888 888
Y8b
Build mode................ spa
Pkg quasar................ v2.15.2
Pkg @quasar/app-webpack... v3.12.4
Pkg webpack............... v5
Debugging................. no
Publishing................ no
Configured browser support (>= 84.21% of global marketshare):
· Chrome for Android >= 125
· Firefox for Android >= 126
· Android >= 125
· Chrome >= 117
· Edge >= 122
· Firefox >= 118
· iOS >= 16.3
· Opera >= 106
· Safari >= 16.6
App • Chaining "UI" Webpack config
App • Extending "UI" Webpack config
App • Cleaned build artifact: "/app/dist/spa"
App • WAIT • Compiling of "UI" in progress...
/app/node_modules/fork-ts-checker-webpack-plugin/lib/rpc/rpc-ipc/RpcIpcMessagePort.js:19
closedError = new RpcIpcMessagePortClosedError_1.RpcIpcMessagePortClosedError(code
^
RpcIpcMessagePortClosedError: Process 31 exited [SIGKILL].
at /app/node_modules/fork-ts-checker-webpack-plugin/lib/rpc/rpc-ipc/RpcIpcMessagePort.js:19:23
at Generator.next (<anonymous>)
at /app/node_modules/fork-ts-checker-webpack-plugin/lib/rpc/rpc-ipc/RpcIpcMessagePort.js:8:71
at new Promise (<anonymous>)
at __awaiter (/app/node_modules/fork-ts-checker-webpack-plugin/lib/rpc/rpc-ipc/RpcIpcMessagePort.js:4:12)
at ChildProcess.handleExit (/app/node_modules/fork-ts-checker-webpack-plugin/lib/rpc/rpc-ipc/RpcIpcMessagePort.js:18:42)
at ChildProcess.emit (node:events:517:28)
at ChildProcess._handle.onexit (node:internal/child_process:292:12) {
code: null,
signal: 'SIGKILL'
}
Node.js v18.20.3
The command '/bin/sh -c quasar build' returned a non-zero code: 1
Based on some other similar errors on other projects, it could also be a memory issue. Do you have enough free memory during building? What command did you use to build? With which version of docker?
i tried reversing the changes in this PR but still getting the same error.
the original error with v1.3.0: