Document option for daemon config validation#3108
Conversation
|
I moved this temporarily to "draft", pending moby/moby#42393 to be merged |
aiordache
force-pushed
the
validate_dockerd_config
branch
from
99b8ec3 to
cf1442d
Compare
Codecov Report
@@ Coverage Diff @@
## master #3108 +/- ##
=======================================
Coverage 56.96% 56.96%
=======================================
Files 299 299
Lines 18733 18733
=======================================
Hits 10672 10672
Misses 7193 7193
Partials 868 868 |
|
moved out of draft as moby PR was merged, but it needs a minor update (I'll leave a comment) |
1 similar comment
|
moved out of draft as moby PR was merged, but it needs a minor update (I'll leave a comment) |
|
|
||
| ```console | ||
| $ dockerd --validate --config-file=/tmp/valid-config.json | ||
| Config OK |
There was a problem hiding this comment.
This changed to
| Config OK | |
| configuration OK |
There was a problem hiding this comment.
Should we also mention that the exit status will be 0 (success) and non-zero (failure)? as that's the "actual" check (message that's printed is informational)?
aiordache
force-pushed
the
validate_dockerd_config
branch
3 times, most recently
from
c09cb25 to
64b2e95
Compare
Signed-off-by: Anca Iordache <[email protected]>
4 participants
We are adding a
--validateoption to dockerd to check if the config file is valid without starting the daemon.Related to moby/moby#42393
- What I did
Added
--validateoption to the docker daemon options documentation.- Description for the changelog
Update documentation and shell completion for the daemon validation option.