run-llama / chat-llamaindex

https://chat.llamaindex.ai
MIT License
761 stars 245 forks source link

[Bug] Addition of Sentry seems to have broken the docker build #89

Open scottmoney opened 2 months ago

scottmoney commented 2 months ago

Describe the bug I clone the main branch and followed the docker build instructions. Instead of having a working docker container I get the following error.

To Reproduce Steps to reproduce the behavior:

  1. clone git clone https://github.com/run-llama/chat-llamaindex
  2. Copy cp .env.template .env.development.local
  3. Build docker build -t chat-llamaindex .
  4. See error
    => [build 2/6] WORKDIR /usr/src/app                                                                                                 0.8s
    => [runtime 2/6] WORKDIR /usr/src/app                                                                                               0.8s
    => [build 3/6] COPY package.json pnpm-lock.yaml ./                                                                                  0.0s
    => [build 4/6] RUN npm install -g pnpm &&     pnpm install                                                                         14.6s
    => [build 5/6] COPY . .                                                                                                             0.3s
    => ERROR [build 6/6] RUN pnpm build                                                                                                39.5s
    ------
    > [build 6/6] RUN pnpm build:
    0.674
    0.674 > chat-llamaindex@ build /usr/src/app
    0.674 > next build
    0.674
    1.363 Attention: Next.js now collects completely anonymous telemetry regarding usage.
    1.363 This information is used to shape Next.js' roadmap and prioritize features.
    1.363 You can learn more, including how to opt-out if you'd not like to participate in this anonymous program, by visiting the following URL:
    1.363 https://nextjs.org/telemetry
    1.363
    1.419   ▲ Next.js 14.2.1
    1.419
    1.475    Creating an optimized production build ...
    1.810 warn  - It seems like you don't have a global error handler set up. It is recommended that you add a global-error.js file with Sentry instrumentation so that React rendering errors are reported to Sentry. Read more: https://docs.sentry.io/platforms/javascript/guides/nextjs/manual-setup/#react-render-errors-in-app-router
    38.00 Failed to compile.
    38.00
    38.00 Sentry CLI Plugin: Command failed: /usr/src/app/node_modules/.pnpm/@sentry+cli@1.77.3_encoding@0.1.13/node_modules/@sentry/cli/sentry-cli releases new VRbevAbU_2mYJxqEuyKqu
    38.00 error: API request failed
    38.00   caused by: [60] SSL peer certificate or SSH remote key was not OK (SSL certificate problem: unable to get local issuer certificate)
    38.00
    38.00 Add --log-level=[info|debug] or export SENTRY_LOG_LEVEL=[info|debug] to see more output.
    38.00 Please attach the full debug log to all bug reports.
    38.00
    38.00 Sentry CLI Plugin: Command failed: /usr/src/app/node_modules/.pnpm/@sentry+cli@1.77.3_encoding@0.1.13/node_modules/@sentry/cli/sentry-cli releases new VRbevAbU_2mYJxqEuyKqu
    38.00 error: API request failed
    38.00   caused by: [60] SSL peer certificate or SSH remote key was not OK (SSL certificate problem: unable to get local issuer certificate)
    38.00
    38.00 Add --log-level=[info|debug] or export SENTRY_LOG_LEVEL=[info|debug] to see more output.
    38.00 Please attach the full debug log to all bug reports.
    38.00
    38.01
    38.01 > Build failed because of webpack errors
    38.22  ELIFECYCLE  Command failed with exit code 1.
    ------
    Dockerfile:18
    --------------------
    16 |
    17 |     # Build the application for production
    18 | >>> RUN pnpm build
    19 |
    20 |     # ---- Production Stage ----
    --------------------
    ERROR: failed to solve: process "/bin/sh -c pnpm build" did not complete successfully: exit code: 1

    Expected behavior The docker build should finish without error Deployment

    • [ x ] Docker
    • [ ] Vercel
    • [ ] Server

Desktop (please complete the following information):