fix: add missing librocksdb8.9 to Dockerfile

[tedil]

Summary by CodeRabbit

• Chores
  • Updated dependency installation in the Dockerfile to include a new version of the RocksDB library.

[coderabbitai]

Walkthrough

The changes involve modifications to the Dockerfile located in the utils/docker directory. The primary update is in the runtime section where the dependency installation has been altered. The installation now includes librocksdb8.9 alongside libsqlite3-0, indicating an upgrade to the RocksDB library version. Other sections of the Dockerfile, including the builder section, entrypoint script, and exposed port, remain unchanged.

Changes

File	Change Summary
utils/docker/Dockerfile	Updated dependency installation from libsqlite3-0 to librocksdb8.9 libsqlite3-0.

Possibly related PRs

• chore: switch docker base image to ubuntu noble, use system rocksdb for faster compilation #555: The changes in this PR involve updating the Dockerfile to use the ubuntu:noble base image and modifying dependency installations, which directly relates to the changes made in the main PR regarding the Dockerfile and the installation of librocksdb8.9.

Poem

🐇 In the Docker world, we make a change,
With RocksDB now, we rearrange.
From sqlite's grasp, we take a leap,
New dependencies, our code to keep.
Hopping along, our app's on track,
With fresh updates, there’s no looking back! 🌟

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Files that changed from the base of the PR and between 8bff7e3 and fbe80fa.

📒 Files selected for processing (1)

• utils/docker/Dockerfile (1 hunks)

🧰 Additional context used

🔇 Additional comments (1)

utils/docker/Dockerfile (1)

60-60: Approved: Addition of librocksdb8.9 addresses the PR objective.

The change successfully adds the missing librocksdb8.9 library to the runtime environment, which aligns with the PR objective. This is a good, focused change that should resolve the issue at hand.

Some suggestions for further improvement:

1. Consider adding a comment explaining why librocksdb8.9 is needed in the runtime environment.
2. It might be beneficial to align the RocksDB versions between the build and runtime environments. The builder section uses librocksdb-dev without a version specification. Consider updating it to match the runtime version if appropriate.

Would you like me to propose a diff that includes these suggestions?

To ensure this change resolves the underlying issue, please run the following verification script:

This script will build the Docker image, verify that librocksdb8.9 is correctly installed, and attempt to run the application to check for any runtime errors.

---

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>, please review it.
  • 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 gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @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.