diff options
| author | D Delmar Davis <don@suspectdevices.com> | 2025-12-11 09:00:52 -0800 |
|---|---|---|
| committer | D Delmar Davis <don@suspectdevices.com> | 2025-12-11 09:00:52 -0800 |
| commit | a6e2f0f574e867007cebb59a88b132d3e1cd9ebf (patch) | |
| tree | b09e9abd697b7d73018f1a9764e78462d72f18ad | |
| parent | eeb015a02e1db491b31dc22cd3df74130133de0d (diff) | |
Blessed by MHix
| -rw-r--r-- | docs/rethinkeverything/k8s-Docker/makingdockerbehave.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/rethinkeverything/k8s-Docker/makingdockerbehave.md b/docs/rethinkeverything/k8s-Docker/makingdockerbehave.md index a29c74c..10c21c0 100644 --- a/docs/rethinkeverything/k8s-Docker/makingdockerbehave.md +++ b/docs/rethinkeverything/k8s-Docker/makingdockerbehave.md @@ -59,7 +59,7 @@ for their containers. ### Health Checks -(This is mostly @mhix but it stands as common sense and within the bounds of docker documentation, I will discuss the issues of using it verbatum) +(This is mostly from Mike Hix I and is used with his permission) All docker containers on docker hosts should have health checks. A health check is a way that docker can programmatically check the health of your service(s). For each service, you’ll need to provide a command and timing parameters. This enables docker to take action based on the health of your service. It also allows someone to see that the container is healthy in the way you intend. |