Files
runc/schema
W. Trevor King ecf73148cb config: Require strictly-positive timeout values
If the timeout value was zero, the hook would always error, and there
doesn't seem to be much point to that.  And I'm not sure what negative
timeouts would mean.  By adding this restriction, we do not limit
useful hook entries, and we give the validation code grounds to warn
users attempting to validate configs which are poorly defined or have
useless hook entries.

I'd like to remove the pointer from the Go type to comply with our
anti-pointer zero-value style (style.md) now that Go's zero-value is
clearly invalid.  However, there has been maintainer resistance to
removing the pointer [1] (although I don't think this is consistent
with previous maintainer statements that we don't need pointers when
the zero value is invalid [2]).  In order to land the normative spec
change, this commit keeps the current *int for Hook.Timeout and punts
a consistent policy to future work.

[1]: https://github.com/opencontainers/runtime-spec/pull/764#discussion_r111607155
[2]: https://github.com/opencontainers/runtime-spec/pull/653#issuecomment-272253010

Signed-off-by: W. Trevor King <wking@tremily.us>
2017-04-15 10:18:29 -07:00
..
2017-02-27 09:29:01 +08:00

JSON schema

Overview

This directory contains the JSON Schema for validating JSON covered by this specification.

The layout of the files is as follows:

Utility

There is also included a simple utility for facilitating validation. To build it:

export GOPATH=`mktemp -d`
go get -d ./...
go build ./validate.go
rm -rf $GOPATH

Or you can just use make command to create the utility:

make validate

Then use it like:

./validate config-schema.json <yourpath>/config.json

Or like:

./validate https://raw.githubusercontent.com/opencontainers/runtime-spec/v1.0.0-rc1/schema/schema.json <yourpath>/config.json