Closed r4nchy closed 2 days ago
Are you by any chance running an old version of hoarder? We added healthchecks a while ago
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.
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.
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
Have you searched for an existing open/closed issue?
Additional context
No response