[GH-ISSUE #696] Add healthchecks for all the containers #450

Closed
opened 2026-03-02 11:49:58 +03:00 by kerem · 3 comments
Owner

Originally created by @r4nchy on GitHub (Nov 25, 2024).
Original GitHub issue: https://github.com/karakeep-app/karakeep/issues/696

Describe the feature you'd like

I wish that hoarder should have a standard container healthcheck in the docker container.

I helps in monitoring docker containers

Describe the benefits this would bring to existing Hoarder users

This would make troubleshooting easy as to which container is healthy or unhealthy.

Can the goal of this request already be achieved via other means?

It was achievable using the following in the compose file, but doesn't seem to work anymore. and few other hoarder containers don't have healthchecks as well

    healthcheck:
      test: ["CMD-SHELL", "ss -lnt | grep ':3000' || exit 1"]
      interval: 30s
      timeout: 5s
      retries: 3
      start_period: 10s
      ```

### Have you searched for an existing open/closed issue?

- [X] I have searched for existing issues and none cover my fundamental request

### Additional context

_No response_
Originally created by @r4nchy on GitHub (Nov 25, 2024). Original GitHub issue: https://github.com/karakeep-app/karakeep/issues/696 ### Describe the feature you'd like I wish that hoarder should have a standard [container healthcheck](https://docs.docker.com/reference/compose-file/services/#healthcheck) in the docker container. I helps in monitoring docker containers ![](https://i.imgur.com/PQteBpj.png) ### Describe the benefits this would bring to existing Hoarder users This would make troubleshooting easy as to which container is healthy or unhealthy. ### Can the goal of this request already be achieved via other means? It was achievable using the following in the compose file, but doesn't seem to work anymore. and few other hoarder containers don't have healthchecks as well ``` healthcheck: test: ["CMD-SHELL", "ss -lnt | grep ':3000' || exit 1"] interval: 30s timeout: 5s retries: 3 start_period: 10s ``` ### Have you searched for an existing open/closed issue? - [X] I have searched for existing issues and none cover my fundamental request ### Additional context _No response_
kerem closed this issue 2026-03-02 11:49:58 +03:00
Author
Owner

@MohamedBassem commented on GitHub (Nov 25, 2024):

Are you by any chance running an old version of hoarder? We added healthchecks a while ago

<!-- gh-comment-id:2497402197 --> @MohamedBassem commented on GitHub (Nov 25, 2024): Are you by any chance running an old version of hoarder? We added healthchecks a while ago
Author
Owner

@r4nchy commented on GitHub (Nov 30, 2024):

and it works, however now I have this different issue of database incompatibility

2024-11-30T01:45:00.668297Z ERROR meilisearch: error=Your database version (1.6.2) is incompatible with your current engine version (1.11.1).
To migrate data between Meilisearch versions, please follow our guide on https://www.meilisearch.com/docs/learn/update_and_migration/updating.
Error: Your database version (1.6.2) is incompatible with your current engine version (1.11.1).
To migrate data between Meilisearch versions, please follow our guide on https://www.meilisearch.com/docs/learn/update_and_migration/updating.
2024-11-30T01:45:04.374261Z ERROR meilisearch: error=Your database version (1.6.2) is incompatible with your current engine version (1.11.1).
To migrate data between Meilisearch versions, please follow our guide on https://www.meilisearch.com/docs/learn/update_and_migration/updating.
Error: Your database version (1.6.2) is incompatible with your current engine version (1.11.1).
To migrate data between Meilisearch versions, please follow our guide on https://www.meilisearch.com/docs/learn/update_and_migration/updating.
<!-- gh-comment-id:2508780478 --> @r4nchy commented on GitHub (Nov 30, 2024): and it works, however now I have this different issue of database incompatibility ``` 2024-11-30T01:45:00.668297Z ERROR meilisearch: error=Your database version (1.6.2) is incompatible with your current engine version (1.11.1). To migrate data between Meilisearch versions, please follow our guide on https://www.meilisearch.com/docs/learn/update_and_migration/updating. Error: Your database version (1.6.2) is incompatible with your current engine version (1.11.1). To migrate data between Meilisearch versions, please follow our guide on https://www.meilisearch.com/docs/learn/update_and_migration/updating. 2024-11-30T01:45:04.374261Z ERROR meilisearch: error=Your database version (1.6.2) is incompatible with your current engine version (1.11.1). To migrate data between Meilisearch versions, please follow our guide on https://www.meilisearch.com/docs/learn/update_and_migration/updating. Error: Your database version (1.6.2) is incompatible with your current engine version (1.11.1). To migrate data between Meilisearch versions, please follow our guide on https://www.meilisearch.com/docs/learn/update_and_migration/updating. ```
Author
Owner

@MohamedBassem commented on GitHub (Nov 30, 2024):

Meillisearch is not backward compatible and you seem to have upgraded it. So either downgrade its version back to 1.6.2 or wipe the meillisearch volume and trigger a reindex (usually very fast) from the admin panel.

<!-- gh-comment-id:2508789058 --> @MohamedBassem commented on GitHub (Nov 30, 2024): Meillisearch is not backward compatible and you seem to have upgraded it. So either downgrade its version back to 1.6.2 or wipe the meillisearch volume and trigger a reindex (usually very fast) from the admin panel.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/karakeep#450
No description provided.