Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

runtime: Explicitly allow 'start' to not validate config.json #418

Merged
merged 1 commit into from
May 18, 2016
Merged

runtime: Explicitly allow 'start' to not validate config.json #418

merged 1 commit into from
May 18, 2016

Commits on May 2, 2016

  1. runtime: Explicitly allow 'start' to not validate config.json 

    This spec places RFC-2119 requirements on both bundles (bundle.md,
config.md, ...)  and runtimes (runtime.md, runtime-linux.md).  While
it's possible to envision a system where bundle validation is required
before container setup begins, it is also possible to decoupled
validation and allow the runtime to blindly stumble through as far as
it can.

We already link to ocitools and OCT for testing both runtimes and
bundles [1], so users interested in pre-start validation can use those
tools.

This commit explicitly documents the non-requirement and links to
those tools, to make life less surprising for everybody.

[1]: https://github.com/opencontainers/runtime-spec/blob/v0.5.0/implementations.md#testing--tools

Signed-off-by: W. Trevor King <wking@tremily.us>
    @wking
    wking committed May 2, 2016
    Configuration menu
    Copy the full SHA
    d7b5e15 View commit details
    Browse the repository at this point in the history