Fix healthcheck pointing to wrong port (8080 instead of 10078) - #8563
Open
MichelleAntunes wants to merge 1 commit into
Open
Fix healthcheck pointing to wrong port (8080 instead of 10078)#8563MichelleAntunes wants to merge 1 commit into
MichelleAntunes wants to merge 1 commit into
Conversation
Signed-off-by: Michelle Antunes <117948294+MichelleAntunes@users.noreply.github.com>
Author
|
Additional context: found a related upstream issue after opening this PR — mudler/LocalAI#10987 (worker-mode containers permanently unhealthy because the healthcheck always probes the default frontend port). The fix there (#10999) made HEALTHCHECK_ENDPOINT empty-by-default and mode-aware via a healthcheck.sh script. This PR addresses the same root cause — a hardcoded default that doesn't reflect the container's actual runtime configuration — but for the case of a custom port (10078) rather than worker mode. The Nextcloud community container is pinned to quay.io/go-skynet/local-ai:v3.12.1-gpu-vulkan, which predates that upstream fix. Until the pinned base image is bumped, this explicit override remains necessary. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fix healthcheck pointing to wrong port (8080 instead of 10078)'
Problem: The nextcloud-aio-local-ai container is permanently reported as unhealthy, even though the LocalAI service itself works correctly.
Root cause: The base image's built-in HEALTHCHECK reads its target from the HEALTHCHECK_ENDPOINT environment variable, which defaults to http://localhost:8080/readyz. This community container configures LocalAI to listen on port 10078 instead (via LOCALAI_ADDRESS=:10078), but never overrides HEALTHCHECK_ENDPOINT to match — so the healthcheck always probes an empty port and fails.
Fix: Add HEALTHCHECK_ENDPOINT=http://localhost:10078/readyz to the environment array in local-ai.json.
Tested: Manually recreated the container on my own AIO instance with this environment variable added; it now reports healthy, and Context Chat / Nextcloud Assistant continued working normally throughout.
Summary
3. to review, feature component)AI (if applicable)