tooling: basic validation tool for config.json

[philips]

We should wait until the first "draft" is done so we don't rewrite it all the time :)

Basic operation:

• octool lint
• octool validate-state
• anything else?

[kelseyhightower]

@philips What about octool lint, which can help people avoid "doing it wrong"

[kunalkushwaha]

May be octool validate-security for checking container security based on Capabilities and security policies, will be helpful.

[wking]

Has this been superseded by #109? That issue is less targetted (it
also talks about validating runtime actions), but it seems to have
attracted more discussion. In both cases, I'd rather leave config
validation be an external tool 1. See also the existing work on
this in external tools 2.

 Message-ID: <20150826212244.GB21585@odin.tremily.us>

[mrunalp]

We will move this code into github.com/opencontainers/ocitools

[vbatts]

https://github.com/opencontainers/ocitools and https://github.com/opencontainers/specs/tree/master/schema will address this kind of validation.

[vbatts]

We'll leave this open until 1.0, as a tracker that the validation tooling is sufficient.

[vbatts]

actually, closing in favor of the #219 tracker