Fix Docker template data volume

[snvtac]

What

• Mount a named iii_data volume at /app/data in the generated Docker compose template.
• Declare the iii_data volume at the top level.
• Drop the stale 9464 exposure from the generated Dockerfile and compose template.
• Extend the init smoke script to exercise iii project init --docker and assert the generated Docker assets include the data volume.

Why

This fixes the generated-template side of iii-hq/iii#1883. On Linux, the engine image runs as non-root UID 65532 and the configuration worker defaults to ./data/configuration under /app, so fresh iii project init --docker && docker compose up can crash-loop with Permission denied unless /app/data is writable.

Notes

• Companion engine image/fixture PR: Fix Docker data directory permissions iii#1910
• Validation run: YAML parse for this compose file, semantic check for iii_data:/app/data, bash -n scripts/smoke-init.sh, and diff whitespace check.
• Docker smoke was not run here because Docker CLI is unavailable in this environment.

[coderabbitai]

Warning

Review limit reached

@snvtac, we couldn't start this review because you've reached your PR review rate limit.

More reviews will be available in 37 minutes and 18 seconds. Learn how PR review limits work.

Your organization has used up its prepaid credits, and credit purchases are no longer available. Enable the review add-on in the billing tab to keep reviews running — you're only billed for reviews past your plan's rate limits ($0.25/file).

⌛ How to resolve this issue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based credits.

🚦 How do rate limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please see our Fair Usage Limits Policy for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: ec61357c-700d-4d85-90cc-3a6bb6e78f14

📥 Commits

Reviewing files that changed from the base of the PR and between 2fc75e1 and 72a6755.

📒 Files selected for processing (3)

• iii/docker/Dockerfile
• iii/docker/docker-compose.yml
• scripts/smoke-init.sh

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

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