Wrong nginx web root path in container since v0.21 — should be /ragflow/web, not /ragflow/web/dist

[easyfoster163]

Environment:

• RAGFlow version: v0.21.1 (full)
• Deployment: official Docker image infiniflow/ragflow:v0.21.1
• OS: Windows 11 host with Docker Desktop

Observation:

• The Docker image no longer contains /ragflow/web/dist directory.
• All static frontend assets (index.html, JS, CSS) reside directly under /ragflow/web/.

Issue:

• The default ragflow.conf (nginx config) and some docker-compose examples still
  use root /ragflow/web/dist;
• When following those configs, the browser shows 404 or blank page.

Suggested fix:

• From v0.21 onward, change the nginx root directive to /ragflow/web

[Ganesh-403]

@easyfoster163 I think this is a valid observation, but it would be worth confirming whether it's specific to v0.21.1 or only certain image variants.

A quick way to verify is to inspect the container:

docker run --rm -it infiniflow/ragflow:v0.21.1 sh

ls -la /ragflow/web
ls -la /ragflow/web/dist

If /ragflow/web/dist does not exist while /ragflow/web/index.html and the static assets are directly under /ragflow/web, then the nginx configuration should indeed use:

root /ragflow/web;

instead of:

root /ragflow/web/dist;

However, I couldn't find any official release note documenting a frontend directory change in v0.21. The current deployment documentation also doesn't mention manually editing the nginx root directive, suggesting the bundled Docker configuration should already be consistent with the image. :contentReference[oaicite:0]{index=0}

If you've verified this against the official infiniflow/ragflow:v0.21.1 image (without custom modifications), it sounds like the repository's ragflow.conf or accompanying deployment examples may simply be outdated and should be updated to match the container layout.

It would also help if you could share:

• the output of:

  ls -la /ragflow/web

• and whether you're using the nginx configuration bundled in the image or a copied/custom ragflow.conf.

That would confirm whether this is a documentation issue or an image/config mismatch.

If this solves your problem, feel free to mark it as the accepted answer so others can find it easily.

[gitsult4n]

/ragflow/web/dist does exist in the official v0.21.1 image
root /ragflow/web/dist is correct and needs no change

proof from the published manifest of infiniflow/ragflow:v0.21.1
image config history maps layer sha256:a44a5114928a to COPY /ragflow/web/dist /ragflow/web/dist
that layer holds 1048 entries all under ragflow/web/dist/ including ragflow/web/dist/index.html

source at tag v0.21.1 agrees
Dockerfile:211 → COPY --from=builder /ragflow/web/dist /ragflow/web/dist
docker/nginx/ragflow.conf:4 → root /ragflow/web/dist;
docker/docker-compose.yml:40 mounts that same conf into the container

main is unchanged
ragflow.conf.golang:4 ragflow.conf.hybrid:4 ragflow.conf.python:4 and helm/templates/ragflow_config.yaml:25 all use /ragflow/web/dist

why /ragflow/web looks like the web root
Dockerfile:193 also does COPY web web so the frontend source sits there
that source tree has no index.html at its root so it cannot serve anything

so a blank page has a different cause
check docker logs -f ragflow-server and whether a host volume is mounted over /ragflow/web