[Bug]: Frontend builder 4/4 RUN Yarn build error: Command failed with signal "SIGKILL"

[stephfoxy]

What happened?

A bug happened!
When attempting to run 'docker command up' I get a frontend build error:
"Command failed with signal "SIGKILL"

Relevant log output

error Command failed with signal "SIGKILL".
93.33 info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
------
failed to solve: process "/bin/sh -c yarn build" did not complete successfully: exit code: 1

Twitter / LinkedIn details

No response

[dosubot]

Hey @stephfoxy!👋 Good to see you back. Running into some trouble, I see? Let's dive into it.

Based on the error message "Command failed with signal 'SIGKILL'", it seems like the process was forcibly terminated due to running out of memory. This can happen if the Docker container's memory limit is too low for the build process's requirements.

Here are a few steps you can take to troubleshoot this issue:

1. Ensure that the Docker daemon or the specific container has enough allocated memory. Docker Desktop, for example, allows you to adjust the memory allocated to containers in its settings.
2. If the build process for the frontend is memory-intensive, consider optimizing the build process or increasing the available memory to the container.
3. Check if there are any resource limits set in the Docker-compose file (if used) for the service that is failing. You might need to adjust these limits.

In the context of the quivr repository, there are a few similar issues that might provide additional insights:

1. [Bug]: => ERROR [frontend builder 4/4] RUN yarn build suggests fixing ESLint warnings and errors, disabling specific ESLint rules causing the warnings, or ignoring all warnings during the build process.
2. [Bug]: can not use docker-compose -f docker-compose.local.yml up to build Quivr on cloud server suggests ensuring that the NEXT_PUBLIC_SUPABASE_URL and NEXT_PUBLIC_SUPABASE_ANON_KEY environment variables are correctly set in your environment file.
3. [Bug]: Issue with yarn.lock suggests checking your network connection, deleting and regenerating the yarn.lock file, or increasing the network timeout value in the yarn install command in the Dockerfile.
4. Installation issue suggests using the same keys in both front and back-ends .env files.

The exact Docker command being used to start the application is CMD ["uvicorn", "main:app", "--host", "0.0.0.0", "--port", "5050", "--workers", "6"] as per the backend/Dockerfile and cms/quivr/Dockerfile.

The exact version of Node.js being used in the Dockerfile is 18.19.0-alpine. The Dockerfile does not specify an exact version for Yarn. It uses the command yarn global add node-gyp without specifying a version, which means it installs the latest version of node-gyp available at the time the Docker image is built. Therefore, the exact version of Yarn cannot be determined from the Dockerfile alone as per the frontend/Dockerfile.

I hope this helps! If you need further assistance, please provide more details about your Docker setup and the exact steps you're taking to build the frontend.

Sources

• [Bug]: => ERROR [frontend builder 4/4] RUN yarn build
• [Bug]: can not use docker-compose -f docker-compose.local.yml up to build Quivr on cloud server
• [Bug]: Issue with yarn.lock
• Installation issue
• backend/Dockerfile.dev
• cms/quivr/Dockerfile
• backend/Dockerfile
• frontend/Dockerfile

About Dosu

This response is meant to be useful and save you time. It is not meant to be a precise solution, but rather a starting point for your own research.

Help me be more useful! Please leave a 👍 if this is helpful and 👎 if it is irrelevant.

If you want to continue the conversation, start your reply with @dosu-bot.