|
|
@ -107,7 +107,7 @@ The table below shows this endpoint's support for |
|
|
|
status of the check. Prior to Consul 1.0, checks used a single `Script` field |
|
|
|
status of the check. Prior to Consul 1.0, checks used a single `Script` field |
|
|
|
to define the command to run, and would always run in a shell. In Consul |
|
|
|
to define the command to run, and would always run in a shell. In Consul |
|
|
|
1.0, the `Args` array was added so that checks can be run without a shell. The |
|
|
|
1.0, the `Args` array was added so that checks can be run without a shell. The |
|
|
|
`Args` field is deprecated, and you should include the shell in the `Args` to |
|
|
|
`Script` field is deprecated, and you should include the shell in the `Args` to |
|
|
|
run under a shell, eg. `"args": ["sh", "-c", "..."]`. |
|
|
|
run under a shell, eg. `"args": ["sh", "-c", "..."]`. |
|
|
|
|
|
|
|
|
|
|
|
- `DockerContainerID` `(string: "")` - Specifies that the check is a Docker |
|
|
|
- `DockerContainerID` `(string: "")` - Specifies that the check is a Docker |
|
|
|