Post install agenta-web script issue - UNABLE_TO_GET_ISSUER_CERT_LOCALLY

[npdkrasicki]

When cloning and attempting to run docker compose, I am running into problems with the build for agenta-web with the post install script for sentry:

45.95 npm error Error: Unable to download sentry-cli binary from https://downloads.sentry-cdn.com/sentry-cli/2.41.1/sentry-cli-Linux-x86_64.
45.95 npm error Error message: request to https://downloads.sentry-cdn.com/sentry-cli/2.41.1/sentry-cli-Linux-x86_64 failed, reason: unable to get local issuer certificate
45.95 npm error Error code: UNABLE_TO_GET_ISSUER_CERT_LOCALLY

Things tried:

• added corporate proxies to the environment and to npm config
• added corporate root CA Certificates to the environment and npm config
• added include=optional to the npm ci command

To get a more verbose error message, I added the below to dev.Dockerfile:

'''
RUN cd /app
&& npm install @sentry/cli --no-optional --verbose
&& NODE_EXTRA_CA_CERTS=/etc/ssl/certs/ca-certificates.crt node ./node_modules/@sentry/cli/scripts/install.js
'''

Here is where docker compose starts to fail:

'''
41.46 npm info run [email protected] postinstall { code: 0, signal: null }
42.11 npm info run @sentry/[email protected] postinstall { code: 1, signal: null }
42.25 npm info run [email protected] postinstall { code: 1, signal: null }
45.95 npm verbose stack Error: command failed
45.95 npm verbose stack at promiseSpawn (/usr/local/lib/node_modules/npm/node_modules/@npmcli/promise-spawn/lib/index.js:22:22)
45.95 npm verbose stack at spawnWithShell (/usr/local/lib/node_modules/npm/node_modules/@npmcli/promise-spawn/lib/index.js:124:10)
45.95 npm verbose stack at promiseSpawn (/usr/local/lib/node_modules/npm/node_modules/@npmcli/promise-spawn/lib/index.js:12:12)
45.95 npm verbose stack at runScriptPkg (/usr/local/lib/node_modules/npm/node_modules/@npmcli/run-script/lib/run-script-pkg.js:77:13)
45.95 npm verbose stack at runScript (/usr/local/lib/node_modules/npm/node_modules/@npmcli/run-script/lib/run-script.js:9:12)
45.95 npm verbose stack at /usr/local/lib/node_modules/npm/node_modules/@npmcli/arborist/lib/arborist/rebuild.js:329:17
45.95 npm verbose stack at run (/usr/local/lib/node_modules/npm/node_modules/promise-call-limit/dist/commonjs/index.js:67:22)
45.95 npm verbose stack at /usr/local/lib/node_modules/npm/node_modules/promise-call-limit/dist/commonjs/index.js:84:9
45.95 npm verbose stack at new Promise ()
45.95 npm verbose stack at callLimit (/usr/local/lib/node_modules/npm/node_modules/promise-call-limit/dist/commonjs/index.js:35:69)
45.95 npm verbose pkgid @sentry/[email protected]
45.95 npm error code 1
45.95 npm error path /app/node_modules/@sentry/cli
45.95 npm error command failed
45.95 npm error command sh -c node ./scripts/install.js
45.95 npm error [sentry-cli] Sentry CLI failed to locate the "@sentry/cli-linux-x64" package after installation!
45.95 npm error
45.95 npm error This can happen if you use an option to disable optional dependencies during installation, like "--no-optional", "--ignore-optional", or "--omit=optional". Sentry CLI uses the "optionalDependencies" package.json feature to install the correct binary for your platform and operating system. This post-install script will now try to work around this by manually downloading the Sentry CLI binary from the Sentry CDN. If this fails, you need to remove the "--no-optional", "--ignore-optional", and "--omit=optional" flags for Sentry CLI to work.
45.95 npm error [sentry-cli] Downloading from https://downloads.sentry-cdn.com/sentry-cli/2.41.1/sentry-cli-Linux-x86_64
'''

Any help would be appreciated.

[mmabrouk]

Hey @npdkrasicki , the source of the issue seems a connection / vpn issue that stops you from downloading sentry.
In any case, sentry is only needed for instrumentation, and you can run the platform without it.
I would do the following:

• Remove the sentry package using npm from package.json (cd agenta-web then npm remove sentry)
• Try building from scratch again

If you find any issue while running due to sentry imports (it should not be the case to my knowledge), just go ahead and remove these wherever from the code.

Let me know if that fixes the issue