From 156b1bc40d172e6bb3c1596ae290685d7c9eebcd Mon Sep 17 00:00:00 2001 From: Qiang Huang Date: Mon, 23 May 2016 16:28:14 +0800 Subject: [PATCH] Make path to bundle optional Make it optional looks reasonable to me, and it's what we do in runc now. Signed-off-by: Qiang Huang --- runtime.md | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/runtime.md b/runtime.md index 0ee199035..44fbddb24 100644 --- a/runtime.md +++ b/runtime.md @@ -70,9 +70,10 @@ In particular, the state MUST be serialized as JSON. ### Start -`start ` +`start []` -This operation MUST generate an error if it is not provided a path to the bundle and the container ID to associate with the container. +This operation MUST generate an error if it is not provided the ID of a container. +The path to the bundle is OPTIONAL, the implementation can define it's default path when path to the bundle is absent. If the ID provided is not unique across all containers within the scope of the runtime, or is not valid in any other way, the implementation MUST generate an error. Using the data in `config.json`, that are in the bundle's directory, this operation MUST create a new container. This includes creating the relevant namespaces, resource limits, etc and configuring the appropriate capabilities for the container.