more fixes: apt more robust, versioning support, create_container script

Change-Id: Id4d8b93c935d27919aa945660ad614f8c73368de
Signed-off-by: Stephane Desneux <stephane.desneux@iot.bzh>

1 files changed, 27 insertions, 1 deletions

diff --git a/README.md b/README.md
index 34cfce1..7df5102 100644
--- a/README.md
+++ b/README.md
@@ -45,4 +45,30 @@ In turn, this setup script will:
 
 When the setup script finishes, Docker commits the temporary container in a new image.
 
-This image can then be exported to a tarball and/or pushed to a Docker registry.
\ No newline at end of file
+This image can then be exported to a tarball and/or pushed to a Docker registry.
+
+## Using the generated image
+
+### Grab the image
+
+To publish the image, there are 2 ways: using a docker registry OR exporting to a tarball.
+
+In the first case, using the image is very easy as it can be pulled directly from the registry host using a 'docker pull' command. The main issue with this method is the efficiency: images are not compressed and it takes ages to transfer overlays to the client host.
+
+In the second case, the efficiency is better but requires to transfer the image archive manually. On the client host, loading the image is as simple as:
+
+```
+# wget -O - <archive_url> | docker load
+```
+
+### Instantiate a container
+
+The following command can be used as an example to instantiate a container:
+
+
+```
+# ./create_container 0
+```
+
+To instantiate more containers on the same host, the instance ID passed as argument must be different from the previous ones.
+