feature/docker starter #5670

bealers · 2025-07-23T13:15:34Z

Docker Infrastructure for elizaOS - foundation stage

Adds Docker support with CLI integration and organized target structure for both starter projects and monorepo development.

New Commands

# Development with hot reload
elizaos dev --docker

# Production deployment  
elizaos start --docker

How It Works

Starter Project Context

When using elizaos create my-project, the generated project includes Docker configs:

elizaos create my-project
cd my-project
elizaos dev --docker    # Starts containerized dev environment
elizaos start --docker  # Starts production-ready container

Benefits:

Consistent environments across team members
No local dependency conflicts (Node versions, system packages)
One-command setup for new developers
Production-like testing locally

Monorepo Context

For ElizaOS core development, use organized Docker targets:

# Development
cd docker/targets/dev && docker-compose up

# Production
cd docker/targets/prod && docker-compose up

# Documentation
cd docker/targets/docs && docker-compose up

Structure

docker/targets/
├── dev/     # Development: hot reload, debug ports, volume mounting
├── prod/    # Production: optimized builds, health checks, PostgreSQL
└── docs/    # Documentation: fast nginx serving

Testing

cd docker/tests && bun test

# Test CLI integration
elizaos create test-project
cd test-project
elizaos dev --docker

Compatibility

No breaking changes
TEE functionality preserved (tee-docker-compose.yaml)
Project starter templates include Docker configs

Review skipped

Auto reviews are disabled on this repository.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

✨ Finishing Touches

🧪 Generate unit tests

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

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

graphite-app · 2025-07-23T13:15:41Z

How to use the Graphite Merge Queue

Add either label to this PR to merge it via the merge queue:

merge-queue - adds this PR to the back of the merge queue
merge-queue-hotfix - for urgent hot fixes, skip the queue and merge this PR next

You must have a Graphite account in order to use the merge queue. Sign up using this link.

_{An organization admin has enabled the Graphite Merge Queue in this repository.} _{Please do not merge from GitHub as this will restart CI on PRs being processed by the merge queue.}

docker/tests/e2e.test.ts

+    if (!projectExists || !pluginsInstalled) {
+      console.log('📦 Creating test project...');
+
+      execSync(`${cliCommand} create --type project --yes e2e-test-project`, {


docker/tests/e2e.test.ts

+
+    // Test CLI --docker flag availability
+    console.log('🔧 Testing CLI --docker flag...');
+    const helpOutput = execSync(`${cliCommand} start --help`, { encoding: 'utf8' });


packages/cli/src/utils/docker-utils.ts

+    logger.info('💡 Press Ctrl+C to stop the container');
+
+    try {
+      const child = exec(`docker ${dockerArgs.join(' ')}`, { cwd: this.projectRoot });


bealers · 2025-07-30T08:57:34Z

ok, lmk when you are ready

…

On Thu, 24 Jul 2025 at 05:51, cjft ***@***.***> wrote: *ChristopherTrimboli* left a comment (elizaOS/eliza#5670) <#5670 (comment)> we need to move this to a branch on eliza repo, hard to test and backport upstream on your fork, I'll reach out and give perms please re-PR with branch based off latest develop your changes — Reply to this email directly, view it on GitHub <#5670 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABQ3H32MAMRAL6ARK4HYDNT3KBQ6PAVCNFSM6AAAAACCF22NOWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTCMJRHE2TINZWGQ> . You are receiving this because you authored the thread.Message ID: ***@***.***>

bealers added 5 commits July 22, 2025 22:38

docker configs for 4x targets[D

bd73fd0

feat:cli added - all 4 container targets work - testing starts

d44b28a

feat: tests added

9962b6d

docs: added temp DOCKER.md and goet teh docs container working

493356e

Merge branch 'elizaOS:develop' into feature/docker-starter

1346270

bealers added 2 commits July 23, 2025 14:22

fix:unused file

8051641

docs: removed some fluff

d7e2b2e

github-advanced-security bot found potential problems Jul 23, 2025

View reviewed changes

wtfsayo self-requested a review August 1, 2025 16:28

ChristopherTrimboli force-pushed the develop branch from 719ff96 to 26469ee Compare August 31, 2025 17:17

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

feature/docker starter #5670

feature/docker starter #5670

Uh oh!

bealers commented Jul 23, 2025 •

edited

Loading

Uh oh!

coderabbitai bot commented Jul 23, 2025

Review skipped

Chat

Support

CodeRabbit Commands (Invoked using PR comments)

Other keywords and placeholders

CodeRabbit Configuration File (`.coderabbit.yaml`)

Documentation and Community

Uh oh!

graphite-app bot commented Jul 23, 2025

Uh oh!

Check warning

Check warning

Check warning

bealers commented Jul 30, 2025 via email

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

feature/docker starter #5670

Are you sure you want to change the base?

feature/docker starter #5670

Uh oh!

Conversation

bealers commented Jul 23, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Docker Infrastructure for elizaOS - foundation stage

New Commands

How It Works

Starter Project Context

Monorepo Context

Structure

Testing

Compatibility

Next

Uh oh!

coderabbitai bot commented Jul 23, 2025

Review skipped

Chat

Support

CodeRabbit Commands (Invoked using PR comments)

Other keywords and placeholders

CodeRabbit Configuration File (.coderabbit.yaml)

Documentation and Community

Uh oh!

graphite-app bot commented Jul 23, 2025

How to use the Graphite Merge Queue

Uh oh!

Check warning

Uh oh!

Check warning

Uh oh!

Check warning

Uh oh!

Uh oh!

bealers commented Jul 30, 2025 via email

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

bealers commented Jul 23, 2025 •

edited

Loading

CodeRabbit Configuration File (`.coderabbit.yaml`)