Skip to content

fix(local-ai): correct healthcheck endpoint port - #8482

Open
bitsandbots wants to merge 1 commit into
nextcloud:mainfrom
bitsandbots:fix/local-ai-healthcheck-endpoint
Open

fix(local-ai): correct healthcheck endpoint port#8482
bitsandbots wants to merge 1 commit into
nextcloud:mainfrom
bitsandbots:fix/local-ai-healthcheck-endpoint

Conversation

@bitsandbots

Copy link
Copy Markdown

Summary

  • nextcloud-aio-local-ai (community container, ghcr.io/docjyj/aio-local-ai-vulkan) reports unhealthy indefinitely even when the service is functioning normally and serving requests.
  • The image's default HEALTHCHECK probes http://localhost:8080/readyz, but LocalAI is configured via LOCALAI_ADDRESS=:10078 and actually listens on port 10078 (confirmed in the container's own startup log: LocalAI is started and running address=":10078", and in the port mapping).
  • Adds an explicit HEALTHCHECK_ENDPOINT=http://localhost:10078/readyz env var to override the image's default and point the health check at the correct port.

Observed in production: 977 consecutive failed health checks over ~16 hours while /models, /chat/completions, and /images/generations all returned 200.

Test plan

  • Validated community-containers/local-ai/local-ai.json is well-formed JSON
  • Maintainers/CI to confirm HEALTHCHECK_ENDPOINT is respected by ghcr.io/docjyj/aio-local-ai-vulkan (env var support confirmed via image's healthcheck script convention, not exhaustively verified against image source)

Healthcheck was probing localhost:8080/readyz but LocalAI listens
on :10078, causing the container to report unhealthy indefinitely
even though the service was responding normally.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
@szaimen

szaimen commented Jul 31, 2026

Copy link
Copy Markdown
Collaborator

@bitsandbots can you plese fix DCO?

@szaimen szaimen added 2. developing Work in progress enhancement New feature or request labels Jul 31, 2026
@szaimen szaimen modified the milestones: next, v13.5.0 Jul 31, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

2. developing Work in progress enhancement New feature or request

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants