Skip to content

Commit 1a6cb18

Browse files
committed
config: Require hook support on Linux and Solaris
Clarifying the language from 28e8f68 (Hooks to linux,solaris and doc clarification, 2017-05-24, #855), which did not say which platforms support hooks and which don't. Without something like this commit, there's no clear way for config authors to know if their runtime will support hooks or not, and there was previous agreement that that sort of ambiguity was not helpful [1]. This also gives normative Markdown grounding for the Go platform tag added in 28e8f68. [1]: #472 (comment) Signed-off-by: W. Trevor King <[email protected]>
1 parent 0bdeae6 commit 1a6cb18

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

config.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -362,9 +362,9 @@ Runtime implementations MAY support any valid values for platform-specific field
362362
}
363363
```
364364

365-
## <a name="configHooks" />Hooks
365+
## <a name="configHooks" />Linux and Solaris Hooks
366366

367-
Hooks allow for the configuration of custom actions related to the [lifecycle](runtime.md#lifecycle) of the container if supported by the platform.
367+
For Linux- and Solaris-based systems, the configuration structure supports `hooks` for configuring custom actions related to the [lifecycle](runtime.md#lifecycle) of the container.
368368

369369
* **`hooks`** (object, OPTIONAL) MAY contain any of the following properties:
370370
* **`prestart`** (array of objects, OPTIONAL) is an array of [pre-start hooks](#prestart).

0 commit comments

Comments
 (0)