fix: resolve container name conflicts in multi-user environments

[SaladDay]

Summary

Remove hardcoded container_name from all services (postgres, redis, app) in docker-compose.yaml to resolve container name conflicts when multiple users share the same Docker daemon.

Problem

When multiple users share the same Docker daemon and run docker compose up, container name conflicts occur because of hardcoded container_name values:

• container_name: claude-code-hub-db
• container_name: claude-code-hub-redis
• container_name: claude-code-hub-app

This causes one user's containers to be overwritten or replaced by another user's deployment.

Related Issues:

• Closes Hardcoded container_name causes conflicts in multi-user environments #624 - Hardcoded container_name causes conflicts in multi-user environments

Solution

Remove all hardcoded container_name values, letting Docker Compose auto-generate names based on the project name. Users can now use the -p flag or set COMPOSE_PROJECT_NAME in their .env file for complete project isolation:

# Option 1: Use -p flag
docker compose -p my-instance up -d

# Option 2: Set in .env
COMPOSE_PROJECT_NAME=my-instance
docker compose up -d

Containers will be automatically named {project}-postgres-1, {project}-redis-1, {project}-app-1.

Changes

File	Change
docker-compose.yaml	Removed container_name from postgres, redis, and app services

Testing

Manual Testing

1. docker compose up -d - verify works with default project name
2. docker compose -p custom-name up -d - verify containers use custom prefix
3. Two users with different COMPOSE_PROJECT_NAME values are fully isolated

---

Description enhanced by Claude AI

[coderabbitai]

Note

Other AI code review bot(s) detected

CodeRabbit has detected other AI code review bot(s) in this pull request and will avoid duplicating their findings in the review comments. This may lead to a less comprehensive review.

📝 Walkthrough

Walkthrough

在 docker-compose.yaml 中新增顶级 name: ${COMPOSE_PROJECT_NAME:-claude-code-hub} 字段，并从 postgres、redis、app 三个服务中移除各自的 container_name 声明；没有其他网络或健康检查行为变化。

Changes

Cohort / File(s)	变更摘要
Compose 配置 docker-compose.yaml	新增顶级字段 name: ${COMPOSE_PROJECT_NAME:-claude-code-hub}（+1 行）；从 postgres、redis、app 服务中移除 container_name 字段（共 -3 行）。

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 分钟

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title accurately describes the main change: removing hardcoded container names to resolve conflicts in multi-user environments, which is the core objective of this PR.
Description check	✅ Passed	The description is comprehensive and directly related to the changeset, explaining the problem, solution, and testing approach for the container name conflict resolution.
Linked Issues check	✅ Passed	The PR implements the recommended Option 1 + Option 3 solution from issue #624: removing hardcoded container_name values and adding top-level project name configuration with COMPOSE_PROJECT_NAME environment variable.
Out of Scope Changes check	✅ Passed	All changes in docker-compose.yaml are directly related to the linked issue #624 objectives—removing container_name fields and adding project-level name configuration for multi-user isolation.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment

---

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

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[gemini-code-assist]

Summary of Changes

Hello @SaladDay, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request resolves container name conflicts and enhances project isolation in multi-user Docker environments. By removing hardcoded container_name values from the docker-compose.yaml file, the system now relies on Docker Compose's automatic naming conventions. This change allows users to leverage the COMPOSE_PROJECT_NAME environment variable for unique project identification, ensuring that services run by different users on the same Docker daemon do not interfere with each other.

Highlights

• Container Naming Convention: Removed hardcoded container_name declarations from postgres, redis, and app services in docker-compose.yaml. This allows Docker Compose to automatically generate container names based on the project name, improving flexibility and preventing conflicts.
• Multi-User Environment Support: Addressed the problem of container name conflicts in shared Docker daemon environments by removing explicit container names, which enables better project isolation when COMPOSE_PROJECT_NAME is utilized.
• Enhanced Project Isolation: The change facilitates complete project isolation by relying on Docker Compose's default naming behavior, which can be influenced by the COMPOSE_PROJECT_NAME environment variable, preventing one user's docker compose down from affecting another's containers.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request correctly removes hardcoded container_name values to address container name conflicts in multi-user environments. However, the solution is incomplete as it's missing the top-level name property in docker-compose.yaml, which was mentioned in the pull request description. This property is crucial for setting a default project name and ensuring complete project isolation. I've added a critical comment to address this omission.

[gemini-code-assist]

Removing the hardcoded container_name is a good step towards resolving the container name conflicts. However, as per the PR description, this is only part of the solution. The top-level name property is missing, which is critical for project isolation. Without it, Docker Compose will use the directory name as the project name, which can still cause conflicts for users.

Please add the following at the top of the docker-compose.yaml file:

name: ${COMPOSE_PROJECT_NAME:-claude-code-hub}

[github-actions]

[Critical] [LOGIC-BUG] Missing top-level name field that is documented in PR description

Why this is a problem: The PR description explicitly states:

"Add top-level name field with COMPOSE_PROJECT_NAME environment variable support"
"Use the combination of: 1. Top-level name: ${COMPOSE_PROJECT_NAME:-claude-code-hub} for project isolation"

However, the actual diff only removes the container_name lines and does NOT add the promised name field. Without this field, Docker Compose will derive the project name from the directory name, which:

1. Does not provide the documented default of claude-code-hub
2. Does not document the COMPOSE_PROJECT_NAME support in the file itself
3. Contradicts what the PR description claims this change does

Suggested fix:

name: ${COMPOSE_PROJECT_NAME:-claude-code-hub}

services:
  postgres:
    image: postgres:18

Add the name field at the top of the file before the services key to match the documented behavior.

[greptile-apps]

_{1 file reviewed, 1 comment}

_{Edit Code Review Agent Settings | Greptile}

[github-actions]

Code Review Summary

This PR aims to resolve container name conflicts in multi-user environments by removing hardcoded container_name values. However, there is a critical discrepancy between the PR description and the actual implementation - the documented name field addition is missing from the diff.

PR Size: XS

• Lines changed: 3 (0 additions, 3 deletions)
• Files changed: 1

Issues Found

Category	Critical	High	Medium	Low
Logic/Bugs	1	0	0	0
Security	0	0	0	0
Error Handling	0	0	0	0
Types	0	0	0	0
Comments/Docs	0	0	0	0
Tests	0	0	0	0
Simplification	0	0	0	0

Critical Issues (Must Fix)

1. [LOGIC-BUG] The PR description claims to "Add top-level name field with COMPOSE_PROJECT_NAME environment variable support", but the diff only shows deletions of container_name lines. The name: ${COMPOSE_PROJECT_NAME:-claude-code-hub} field is not present in the changes.

   Without the name field:

   • Docker Compose will use the directory name as the project name (not claude-code-hub)
   • The COMPOSE_PROJECT_NAME environment variable support is not explicitly documented in the file
   • The solution described in the PR body is incomplete

   Action Required: Add the top-level name field as documented, or update the PR description to accurately reflect the actual changes.

Review Coverage

• Logic and correctness - Issue found
• Security (OWASP Top 10) - Clean
• Error handling - N/A (config file)
• Type safety - N/A (YAML)
• Documentation accuracy - Mismatch between PR description and implementation
• Test coverage - N/A (infrastructure change)
• Code clarity - Clean

---

Automated review by Claude AI