Add HEALTHCHECK
instruction to Dockerfile
#407
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.
The
Dockerfile
currently does not have aHEALTHCHECK
instruction. Users of the Docker image currently need to add it manually (e.g. via Docker Compose). Instead, theDockerfile
itself should include the instruction.To determine whether the service is healthy, one can use the
PING
command via the Redis CLI, which is already part of the image. The command “is useful for […] verifying the server's ability to serve data”.Most of the default
HEALTHCHECK
options seem reasonable:I set
--start-period=1s
because the default of0s
is too quick for this program.Users of the image can still override the
HEALTHCHECK
instruction if they want to customize the command or the options.