fix: wrong Dockerfile path in docs docker-compose.yaml

[mervivian]

Summary

The docker-compose.yaml in the docs/ directory references dockerfiles/Dockerfile as the build target, but no dockerfiles/ directory exists in the repo. The actual Dockerfile lives at docs/Dockerfile, which is docs/Dockerfile relative to the build context (.., the repo root). Running docker compose up from the docs/ directory fails immediately because Docker can't find the referenced file.

How to reproduce

1. Clone the repo
2. cd docs
3. docker compose up
4. Error: failed to solve: failed to read dockerfile: open dockerfiles/Dockerfile: no such file or directory

Test plan

• Run docker compose up from the docs/ directory after the fix and confirm Docker finds and builds the Dockerfile successfully.

Summary by CodeRabbit

• Chores
  • Updated Docker build configuration path for documentation service.

[CLAassistant]

All committers have signed the CLA.

[coderabbitai]

Important

Review skipped

Auto incremental 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.

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 9540ef44-498f-4842-98b2-adde3a71559f

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

Use the checkbox below for a quick retry:

• 🔍 Trigger review

📝 Walkthrough

Walkthrough

The docs service build configuration in docs/docker-compose.yaml is updated to use a local docs/Dockerfile instead of a centralized dockerfiles/Dockerfile, moving the Dockerfile reference closer to the docs directory structure.

Changes

Docker Compose Configuration

Layer / File(s)	Summary
Docker Compose docs service build path docs/docker-compose.yaml	The docs service build configuration is updated to reference dockerfile: docs/Dockerfile instead of dockerfiles/Dockerfile.

🎯 1 (Trivial) | ⏱️ ~2 minutes

🐰 A single line hops away so clean,
From dockerfiles to docs it's seen,
The build path now is crystal clear,
A tiny change, but right right here! 🏗️

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title accurately identifies the main change: correcting the Dockerfile path reference in the docker-compose.yaml file for the docs service.
Description check	✅ Passed	The description includes the Impact checkbox (Bug fix), a clear Summary of the problem, reproduction steps, and a test plan, covering the essential required sections.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

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

✨ 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 and usage tips.}