[Bug]: make health reports backend as Not responding when backend container is healthy

[NishadA05]

OpenRAG Version

0.5.0

Deployment Method

Podman

Operating System

macOS Tahoe 26.5.1

Python Version

3.14.5

Affected Area

TUI (Terminal User Interface)

Bug Description

make health says the backend is Not responding, even though the backend container is actually healthy.

In my Podman setup, the backend port is not published to the host, so this check fails:

curl http://127.0.0.1:8000/health

But checking the backend from inside the container works:

podman exec openrag-backend curl http://localhost:8000/health

and returns:

{"status":"ok"}

So make health is giving a false negative for the backend. It should either check the backend inside the container or handle setups where the backend port is not published to the host.

Steps to Reproduce

1. Start OpenRAG using Podman.
2. Run:
   make health
3. Notice that the backend is reported as not responding:
   Backend: Not responding
4. Check the backend container directly:
   podman exec openrag-backend curl http://localhost:8000/health
5. Notice that the backend is actually healthy:

{"status":"ok"}

6. Check the backend container ports:
   podman ps

The backend shows internal ports like 8000/tcp, but not a host mapping like 0.0.0.0:8000->8000/tcp.

This means make health is checking the backend from the host, but the backend is only reachable inside the container.

Expected Behavior

Make health should return Backend: Healthy

Actual Behavior

Make Health returns Backend: Not responding

Relevant Logs

Screenshots

No response

Additional Context

No response

Checklist

• I have searched existing issues to ensure this bug hasn't been reported before.
• I have provided all the requested information.

[NishadA05]

Fixed by PR #1883