{{ message }}
Repository navigation
Trying to setup ToolJet with Docker but having problem with the process #14251
Unanswered
Pratik5252
asked this question in
Q&A
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment

Uh oh!
There was an error while loading. Please reload this page.
I tried to follow the docker setup for ToolJet form here - https://docs.tooljet.ai/docs/contributing-guide/setup/docker
When I run
docker compose buildI encounter the following errorError Log
[internal] load build definition from plugins.Dockerfile.dev
transferring 435/0 0.003
[internal] load metadata for docker.io/library/node:18.18.2-bullseye
[internal] load .dockerignore
[1/7] FROM docker.io/library/node:18.18.2-bullseye@sha256:772f910c34bf1419307abe281c8a0b27206359db864fac50781665508a88e7e6
resolve docker.io/library/node:18.18.2-bullseye@sha256:772f910c34bf1419307abe281c8a0b27206359db864fac50781665508a88e7e6 0/0 0.054
[internal] load build context
transferring 2782091/0 0.935
[2/7] RUN npm i -g npm@9.8.1
[4/7] COPY ./package.json ./package.json
[5/7] COPY ./plugins/package.json ./plugins/package-lock.json ./plugins/
[3/7] WORKDIR /app
[6/7] RUN npm --prefix plugins install
npm WARN deprecated w3c-hr-time@1.0.2: Use your platform's native performance.now() and performance.timeOrigin.
npm WARN deprecated read-package-json@5.0.2: This package is no longer supported. Please use @npmcli/package-json instead.
npm WARN deprecated request@2.88.0: request has been deprecated, see request/request#3142
npm WARN deprecated q@1.5.1: You or someone you depend on is using Q, the JavaScript Promise library that gave JavaScript developers strong feelings about promises. They can almost certainly migrate to the native JavaScript promise now. Thank you literally everyone for joining me in this bet against the odds. Be excellent to each other.
npm WARN deprecated
npm WARN deprecated (For a CapTP with native promises, see @endo/eventual-send and @endo/captp)
npm WARN deprecated querystring@0.2.0: The querystring API is considered Legacy. new code should use the URLSearchParams API instead.
npm WARN deprecated rimraf@3.0.2: Rimraf versions prior to v4 are no longer supported
npm WARNdeprecated npmlog@6.0.2: This package is no longer supported.
npm WARN deprecated 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.
npm WARN deprecated har-validator@5.1.5: this library is no longer supported
npm WARN deprecated glob@7.2.3: Glob versions prior to v9 are no longer supported
npm WARN deprecated gauge@4.0.4: This package is no longer supported.
npm WARN deprecated domexception@2.0.1: Use your platform's native DOMException instead
npm WARN deprecated debuglog@1.0.1: Package no longer supported. Contact Support at https://www.npmjs.com/support for more info.
npm WARN deprecated are-we-there-yet@3.0.1: This package is no longer supported.
npmWARN deprecated abab@2.0.6: Use your platform's native atob() and btoa() methods instead
npm notice
npm notice New major version of npm available! 9.8.1 -> 11.6.1
npm notice Changelog: https://github.com/npm/cli/releases/tag/v11.6.1
npm notice Run
npm install -g npm@11.6.1to update!npm notice
npm ERR! code ERR_SOCKET_TIMEOUT
npm ERR! network Socket timeout
npm ERR! network This is a problem related to network connectivity.
npmERR! network In most cases you are behind a proxy or have bad network settings.
npm ERR! network
npm ERR! network If you are behind a proxy, please make sure that the
npmERR! network 'proxy' config is set properly. See: 'npm help config'
This is the same issue with other file client.Dockerfile.dev and server.Dockerfile.dev
Kindly take a look at this
Thank You.
All reactions