Commit Graph

5 Commits

Author SHA1 Message Date
W. Trevor King 713d98102c runtime-config: Remove 'destination' docs from mounts
c18c283 (Change layout of mountpoints and mounts, 2015-09-02, )
removed the destination field from the Go type and examples, but
forgot to remove it from the documentation [1].  Fix that with this
commit.

[1]: https://github.com/opencontainers/specs/issues/109#issuecomment-138531616

Reported-by: 梁辰晔 (Liang Chenye) <liangchenye@huawei.com>
Signed-off-by: W. Trevor King <wking@tremily.us>
2015-09-09 09:45:11 -07:00
Alexander Morozov c18c283a17 Change layout of mountpoints and mounts
Added info about MountPoints to config.md.

Signed-off-by: Alexander Morozov <lk4d4@docker.com>

Signed-off-by: W. Trevor King <wking@tremily.us>
2015-09-02 21:04:44 -07:00
W. Trevor King 284f914909 runtime-config: Remove blank lines from the end of files
These snuck in with 7232e4b1 (specs: introduce the concept of a
runtime.json, 2015-07-30, ) and 73bf1ba8 (JSON objects are easier
to parse/manipulate, 2015-08-27, ).

Signed-off-by: W. Trevor King <wking@tremily.us>
2015-08-28 22:07:58 -07:00
Timothy Hobbs 73bf1ba833
JSON objects are easier to parse/manipulate
Don't use strings when you can use dictionaries/objects. JSON objects are trivial to parse and manipulate, unlike strings. String parsing is the  cause of security bugs, so if it can be trivially avoided, then why not ;)
2015-08-27 22:19:27 +02:00
Brandon Philips 7232e4b137 specs: introduce the concept of a runtime.json
Based on our discussion in-person yesterday it seems necessary to
separate the concept of runtime configuration from application
configuration. There are a few motivators:

- To support runtime updates of things like cgroups, rlimits, etc we
  should separate things that are inherently runtime specific from
  things that are static to the application running in the container.

- To support the goal of being able to move a bundle between hosts we
  should make it clear what parts of the spec are and are not portable
  between hosts so that upon landing on a new host the non-portable
  options may be rewritten or removed.

- In order to attach a cryptographic identity to a bundle we must not
  include details in the bundle that are host specific.
2015-08-26 09:44:09 -07:00