Optimize docker image

[dudizimber]

Related issue #554

To be merged after PR:
FalkorDB/build-image#2

Summary by CodeRabbit

• Refactor
  • Simplified Docker container setup to enhance compatibility and maintenance.
• Chores
  • Updated Redis to version 7.2.4 in Docker images for improved stability and performance.

[coderabbitai]

Walkthrough

The project's Docker setup has been enhanced with a new build stage named "builder," improving the process of managing dependencies and file copying. Additionally, the Dockerfile now explicitly includes Redis version 7.2.4 in the final image. The run.sh script has been streamlined, removing architecture-specific conditions and uniformly setting the MODULE_DIR environment variable, thereby simplifying the deployment process across different platforms.

Changes

File Path	Change Summary
build/docker/Dockerfile	Introduced "builder" stage, added instructions for dependencies and Redis 7.2.4, optimized file copying.
build/docker/run.sh	Simplified MODULE_DIR setting, removed architecture-specific logic.

🐰✨
In the world of code, where changes abound,
A Dockerfile and script were newly crowned.
With a hop and a skip, the setup's refined,
A smoother path ahead, for all to find.
🚀🌟

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-tests for this file.
• 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 tests 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 from git and render them as a table.
  • @coderabbitai show all the console.log statements in this repository.
  • @coderabbitai read src/utils.ts and generate unit tests.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

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 as PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger a review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• The JSON schema for the configuration file is available here.
• 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/coderabbit-overrides.v2.json

CodeRabbit Discord Community

Join our Discord Community to get help, request features, and share feedback.

[coderabbitai]

Review Status

Actionable comments generated: 3

Configuration used: CodeRabbit UI

Commits

Files that changed from the base of the PR and between aa5feb9 and 8a2d90a.

Files selected for processing (2)

• build/docker/Dockerfile (2 hunks)
• build/docker/run.sh (1 hunks)

Files skipped from review due to trivial changes (1)

• build/docker/run.sh

Additional comments: 4

build/docker/Dockerfile (4)

• 1-1: The introduction of a "builder" stage with FROM --platform=$TARGETPLATFORM falkordb/falkordb-build:latest as builder is a good practice for optimizing Docker builds. It allows for separation of the build environment from the runtime environment, which can reduce the final image size.
• 24-24: The COPY instruction uses a wildcard (linux*) to copy the falkordb.so file. This approach assumes a consistent naming convention for directories. Ensure that this assumption holds true across all expected build environments to avoid copy failures.
• 25-25: Setting ENV ARCH=${TARGETPLATFORM} is a good practice for making the architecture information available within the container. This can be useful for scripts or applications that need to adjust behavior based on the underlying architecture.
• 1-4: > 📝 NOTE

This review was outside the diff hunks, and no overlapping diff hunk was found. Original lines [32-32]

The CMD instruction correctly specifies the script to run when the container starts. Ensure that the run.sh script is properly configured to launch FalkorDB with the desired settings and handles any required initialization tasks.

[coderabbitai]

Review Status

Actionable comments generated: 0

Configuration used: CodeRabbit UI

Commits

Files that changed from the base of the PR and between 8a2d90a and 3262ce4.

Files selected for processing (1)

• build/docker/Dockerfile (2 hunks)

Files skipped from review as they are similar to previous changes (1)

• build/docker/Dockerfile