Skip to content

Conversation

@WeiZhang555
Copy link
Contributor

Update example config.json in README.md for it's not workable for new structure

Signed-off-by: Zhang Wei zhangwei555@huawei.com

Update example `config.json` in README.md for it's not workable for new
structure.

Signed-off-by: Zhang Wei <zhangwei555@huawei.com>
@hqhq
Copy link
Contributor

hqhq commented Oct 27, 2015

@WeiZhang555 Thanks for your PR, I'm also working on this. Currently spec is under heavily development, config.json and runtime.json could be updated very soon, so I think we should suggest users always use runc spec to generate JSON files, so we don't have to update this README too often and users can always get the right way to play with runc.

I opened a new PR #371 , what do you think?

@WeiZhang555
Copy link
Contributor Author

@hqhq
I agree with you, maybe we can remove the whole config.json and runtime.json, so user will know that they should always use runc spec to generate necessary config files.

Keep yours, I'll close this duplicate.

stefanberger pushed a commit to stefanberger/runc that referenced this pull request Sep 8, 2017
stefanberger pushed a commit to stefanberger/runc that referenced this pull request Sep 8, 2017
Through 6734c7a (Merge pull request opencontainers#370 from
vbatts/json_schema_and_examples, 2016-04-11).

The only unlisted changes to master were a brief run with ffjson
(opencontainers#343, opencontainers#351), but that was pulled out due to gccgo issues in opencontainers#363.

Signed-off-by: W. Trevor King <wking@tremily.us>
stefanberger pushed a commit to stefanberger/runc that referenced this pull request Sep 8, 2017
To match where they're defined in the JSON Schema [1].  The old
location is from d4e7326 (config: JSON examples, 2016-04-06, opencontainers#370),
and seems to have been accidental.

[1]: https://github.com/opencontainers/runtime-spec/blob/0982071b288ddddc1ae84d21c4bd682c96942f5c/schema/schema-linux.json#L21-L48

Signed-off-by: W. Trevor King <wking@tremily.us>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants