Fix production docker build

[BMartinos]

A couple of issues were causing the Docker build to fail The docker build should now run to completion and push the image to dockerhub

Summary by CodeRabbit

• New Features

  • Updated the base image for the application to a previous version of Node.js, potentially enhancing compatibility.

• Improvements

  • Simplified the dependency installation process, improving clarity and consistency in builds.

[coderabbitai]

Walkthrough

The pull request updates the Dockerfile for a Node.js application by changing the base image from node:22-alpine to node:20-alpine. It simplifies the dependency installation process by removing a multi-condition RUN command and replacing it with a single COPY command for the prisma directory, followed by a streamlined RUN command that uses Yarn with a network timeout and the --frozen-lockfile option.

Changes

File	Change Summary
docker/production/Dockerfile	Updated base image from node:22-alpine to node:20-alpine and simplified dependency installation logic.

Possibly related PRs

• Fix broken Production build #40: Related changes in the Dockerfile also involve updates to the base image version, indicating a direct connection in the modifications.

Poem

🐇 In the land of code where rabbits hop,
We’ve changed our base, now we won’t stop!
With Yarn so swift and locks held tight,
Our app will run smooth, oh what a delight!
From twenty to twenty-two, we’ve made the leap,
In our Docker world, the changes run deep! 🐇

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

Share

• X
• Mastodon
• Reddit
• LinkedIn

Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai generate interesting stats about this repository and render them as a table.
  • @coderabbitai show all the console.log statements in this repository.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[coderabbitai]

Actionable comments posted: 0

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 8c6f885 and c473144.

Files ignored due to path filters (1)

• yarn.lock is excluded by !**/yarn.lock, !**/*.lock

Files selected for processing (1)

• docker/production/Dockerfile (2 hunks)

Additional comments not posted (4)

docker/production/Dockerfile (4)

1-1: Verify compatibility and performance impact due to Node.js version downgrade.

The base image has been changed from node:22-alpine to node:20-alpine. This downgrade could potentially affect the compatibility with dependencies and the overall performance of the application.

Please ensure that all dependencies are compatible with Node.js version 20 and that performance benchmarks are conducted to assess any impact.

---

12-14: Simplified dependency installation logic approved.

The changes to the dependency installation logic, including the addition of the prisma directory and the streamlined RUN command using Yarn with --frozen-lockfile, enhance clarity and ensure consistency with the lockfile. This simplification is beneficial for maintaining reproducible builds.

---

1-1: Multi-stage build setup approved.

The use of a multi-stage build process in this Dockerfile is a best practice that optimizes both the build process and the size of the final Docker image. Each stage is clearly defined and serves a specific purpose, which enhances maintainability and efficiency.

Also applies to: 12-14

---

1-1: Final stage setup and configuration approved.

The configuration in the runner stage of the Dockerfile, including the setup of a non-root user and the appropriate setting of environment variables and exposed ports, follows best practices for security and operational efficiency.

Also applies to: 12-14