[Chainquery] implement HEALTHCHECK #59
Labels
No labels
Accepted
area: devops
area: discovery
area: docs
area: livestream
area: proposal
consider soon
Epic
good first issue
hacktoberfest
help wanted
icebox
In Review
level: 1
level: 2
level: 3
level: 4
needs: exploration
needs: grooming
needs: priority
needs: repro
needs: tech design
on hold
priority: blocker
priority: high
priority: low
priority: medium
resilience
Tom's Wishlist
type: bug
type: discussion
type: improvement
type: new feature
type: refactor
type: task
type: testing
unplanned
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: LBRYCommunity/lbry-docker#59
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Eventually, we need boilerplate health checks for all of the containers shipped with the containers themselves.
I'd like to take this. Although I believe the first healthcheck should be librycrd.
Is there something that can be curl'd in order to determine if chainquery [or librycrd] is ready?
I see this in Dockerfile:
/usr/bin/healthcheck is a script that relies on curl, which isn't installed. I'd like to take a stab getting it to work with lbrycrd-cli
I have a working patch for lbrycrd healthcheck. Let's see if I can get chainquery done tonight.
@dangarthwaite open some PR's!
So - the actual healthcheck for chainquery is untested. A whole lot of other configuration files were tweaked to get lbrycrd running in regtest mode. In the end this ticket is blocked until https://github.com/lbryio/chainquery/issues/121 is fixed.
chainquery serve
gives an error when it starts.What does work are healthcheckers for lbrycrd and mysql containers that are in this PR. Also a rewrite of chainquery/start.sh that ought to be wire-compatible and a LOT easier on the eyes.
For the most part the Chainquery "healthcheck" in this case was just to make sure the process hadn't died and had completed it's initial boot process.
I changed chainquery's Dockerfile to download the latest version. All three containers now have healthchecks.
Fixed by #87