docker
/
docs
mirror of https://github.com/docker/docs.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Additional Documentation 

Added documentation to indicate when to to run the command (prior to submitting for publishing) and added documentation to indicate that warnings are allowed to certify but errors must be fixed.
This commit is contained in:
Gary Forghetti 2018-06-28 14:39:13 -04:00 committed by Joao Fernandes
parent 1a79da3300
commit c6d64230a0
1 changed files with 4 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
docker-store/certify-plugins-logging.md
View File

@ -14,6 +14,8 @@ This page explains how publishers can successfully test their **Docker logging p
> Content that requires a non-certified infrastructure environment cannot be published as certified.
> You should perform this Self Certification test prior to submitting your product for publishing.
## Certify your logging plugins
You must use the tool, `inspectDockerLoggingPlugin`, to certify your content for publication on Docker Store by ensuring that your Docker logging plugins conform to best practices.
@ -28,6 +30,8 @@ The `inspectDockerLoggingPlugin` command verifies that your Docker logging plugi
- Displays the container logs and compares it to `quotes.txt`. If they match, the test is successful.
> The `inspectDockerLoggingPlugin` tool will detect issues and output them as **warnings** or **errors**. **Errors** must be fixed in order to certify. Resolving **warnings** is not required to certify, but you try to resolve them.
The syntax for running a specific logging plugin is: `docker container run --log-driver`.
No parameters are passed to the logging plugin. If parameters are required for the Docker logging plugin to work correctly, then a custom test script must be written and used. The default `docker container run` command is: