fix: remove commands from the docker compose file

[sriramveeraghanta]

Description

• remove commands from the docker compose file

Type of Change

• Bug fix (non-breaking change which fixes an issue)

Summary by CodeRabbit

• Chores
  • Updated service definitions in the deployment configuration to use default startup commands.
  • Reformatted configuration sections for improved consistency without changing functionality.

[coderabbitai]

Walkthrough

The update to the Docker Compose configuration removes explicit command directives from several service definitions, causing them to use the default commands specified in their container images. Additionally, the formatting of some sections in the proxy service is adjusted for consistency, without altering their actual configuration.

Changes

File(s)	Change Summary
deployments/cli/community/docker-compose.yml	Removed explicit command entries from services; reformatted proxy service sections for clarity.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

• feat: Adding Docker CMD in all Dockerfiles #7339: Removes explicit command entries from docker-compose.yml to rely on default container commands, complementing PRs that add default CMD instructions in Dockerfiles for these services.

Poem

🐇
Compose files neat, commands now gone,
Containers start as they move along.
Indents aligned, the proxy’s in line,
Simpler scripts—oh, how divine!
With every hop, this rabbit cheers,
For cleaner code throughout the years.

Note

⚡️ Unit Test Generation is now available in beta!

Learn more here, or try it out under "Finishing Touches" below.

✨ Finishing Touches

🧪 Generate unit tests

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch fix-community-docker-compose

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ 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.
  • Explain this complex logic.
  • 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 explain this code block.
  • @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 explain its main purpose.
  • @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.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

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 generate docstrings to generate docstrings for this PR.
• @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
• @coderabbitai generate unit tests to generate unit tests for this 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

🧹 Nitpick comments (2)

deployments/cli/community/docker-compose.yml (2)

225-233: mode: host ties the proxy ports to the host network

Using the long-syntax ports with mode: host is Swarm-specific; vanilla docker-compose ignores mode and falls back to normal NAT publishing.
If you intend to run this file outside Swarm, consider omitting mode to avoid confusion, or document the environment expectation clearly.

---

235-243: No functional change, but watch for merge conflicts

The reformatted volumes and depends_on blocks are semantically identical; however, large-scale whitespace changes frequently cause rebase pain.
If possible, defer pure-formatting alterations to a dedicated commit to minimise future conflicts.

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 18e4c60 and cc16310.

📒 Files selected for processing (1)

• deployments/cli/community/docker-compose.yml (1 hunks)

🔇 Additional comments (4)

deployments/cli/community/docker-compose.yml (4)

61-71: Removal of command for web may leave the container idle

The web image now relies entirely on its ENTRYPOINT/CMD. If that image was previously started with a custom command (e.g. node server.js or a Next JS start script) and the image itself does not embed one, the container will spin up and immediately exit.
Please confirm the image already defines a suitable default or re-introduce the command here or in the Dockerfile.

---

72-82: Same concern for space service

space also lost its explicit start command. Validate the default command inside plane-space is production-ready; otherwise this change is a breaking one for every deployment that upgrades directly.

---

83-92: admin service now depends on an implicit default command

As with web/space, double-check that the plane-admin image defines a non-blocking default command; otherwise the service will fail health checks and keep restarting.

---

93-104: live service – verify entrypoint coverage

plane-live previously required an explicit command. Ensure its Docker image has been rebuilt with a proper ENTRYPOINT before removing the override here.