[BUG] docker-compose.yml validation fails because frontend service is nested under volumes

[Kishalll]

Description of the Bug

When attempting to start the project using Docker Compose, it fails with a validation error. In docker-
compose.yml (around line 191), the frontend: block is incorrectly indented as a child of the
volumes: section instead of being defined under the services: section.

Steps to Reproduce

1. Clone the repository and navigate to the root directory.
2. Run docker compose --profile cpu up --build
3. See the validation error preventing Docker from starting.

Expected Behavior

Docker Compose should successfully parse the file and build/start the frontend container alongside the
backend services, without throwing volume-related validation errors.

Screenshots / Logs

WARN[0000] The "HF_TOKEN" variable is not set. Defaulting to a blank string.
validating /home/gigabyte/PDF-Assistant-RAG/docker-compose.yml: volumes.frontend additional
properties 'restart', 'build', 'container_name', 'healthcheck', 'ports', 'profiles' not allowed

Environment

OS: Arch Linux (Applies to all operating systems running Docker) , Environment: Docker Compose

GSSoC '26

• Yes, I am participating in GirlScript Summer of Code and would like to fix this.

[github-actions]

Hi @Kishalll! 👋

Thanks for opening this issue! We are thrilled to have you contribute to PDF-Assistant-RAG for GSSoC 2026.

📌 Before you start:

• Make sure you have read our Contributing Guidelines.
• Wait for a project admin to assign this issue to you before working on it.
• Remember to branch off dev and not main.

Happy Coding! 🚀

[Kishalll]

Hi @param20h! I'd love to be assigned to this issue under GSSoC 2026.

My approach:

• Move the frontend: definition block (and all of its child properties like build , ports ,
restart ) out from under the volumes: section in docker-compose.yml .
• Re-indent and place it properly under the services: section so that Docker Compose correctly parses
it as an application service rather than a data volume.