Make the docker info folder configurable through env variables

[bradsawadye]

This is to cater for the ehtipoia use case where the docker folders are stored in a different location

Summary by CodeRabbit

• New Features

  • Enhanced configuration flexibility for Docker services with the introduction of environment variables for volume mappings.
  • Added new configuration parameters for Docker socket and library folder paths.

• Bug Fixes

  • Improved security and adaptability in different deployment environments by replacing hardcoded paths with variable references.

[coderabbitai]

Walkthrough

The recent changes enhance the configurability of Docker services in the monitoring setup. By replacing hardcoded paths with environment variable references, the adjustments allow for more flexible deployment across different environments. New parameters for Docker socket and library paths were also introduced, streamlining configuration management and improving security.

Changes

Files	Change Summary
monitoring/docker-compose.cluster.yml	Volume mapping for Docker socket changed to use ${DOCKER_SOCK_FOLDER}.
monitoring/docker-compose.yml	Volume mappings updated to use environment variables, changing paths for Prometheus, another unspecified service, and promtail to utilize ${DOCKER_SOCK_FOLDER} and ${DOCKER_LIB_FOLDER}.
monitoring/package-metadata.json	Added configuration parameters: "DOCKER_SOCK_FOLDER": "/var/run/docker.sock" and "DOCKER_LIB_FOLDER": "/var/lib/docker/".

Poem

🐰 In a world of Docker, so neat and grand,
Paths now dance, like bunnies in sand.
From hardcoded lines to variables clear,
Configurations blossom—a change we hold dear!
With sockets and libraries, ready to roam,
Flexibility reigns in our coding home! 🌼

---

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 as 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.

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

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 041010b and 5294a79.

Files selected for processing (3)

• monitoring/docker-compose.cluster.yml (1 hunks)
• monitoring/docker-compose.yml (3 hunks)
• monitoring/package-metadata.json (1 hunks)

Additional comments not posted (6)

monitoring/package-metadata.json (2)

38-38: LGTM! New environment variable for Docker socket folder.

The addition of DOCKER_SOCK_FOLDER enhances configurability.

---

39-39: LGTM! New environment variable for Docker library folder.

The addition of DOCKER_LIB_FOLDER enhances configurability.

monitoring/docker-compose.cluster.yml (1)

21-21: LGTM! Updated volume mapping for Docker socket.

The change to use ${DOCKER_SOCK_FOLDER} enhances configurability.

monitoring/docker-compose.yml (3)

78-78: LGTM! Updated volume mapping for Prometheus service.

The change to use ${DOCKER_SOCK_FOLDER} enhances configurability.

---

100-100: LGTM! Updated volume mapping for Docker library.

The change to use ${DOCKER_LIB_FOLDER} enhances configurability.

---

134-134: LGTM! Updated volume mapping for promtail service.

The change to use ${DOCKER_LIB_FOLDER}/containers enhances configurability.

[rcrichton]

LGTM

[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 5294a79 and 74af76b.

Files selected for processing (1)

• monitoring/docker-compose.yml (3 hunks)

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

• monitoring/docker-compose.yml