@@ -62,6 +62,18 @@ func loadLongDescription(cmd *cobra.Command, path string) error {

 			return err

 		}

 		cmd.Long = string(content)

+

+		fullpath = filepath.Join(path, cmd.Name()+"-example.md")

+		if _, err := os.Stat(fullpath); err != nil {

+			continue

+		}

+

+		content, err = ioutil.ReadFile(fullpath)

+		if err != nil {

+			return err

+		}

+		cmd.Example = string(content)

+

 	}

 	return nil

 }

new file mode 100644

@@ -0,0 +1,35 @@

+### Specify isolation technology for container (--isolation)

+

+This option is useful in situations where you are running Docker containers on

+Windows. The `--isolation=<value>` option sets a container's isolation

+technology. On Linux, the only supported is the `default` option which uses

+Linux namespaces. On Microsoft Windows, you can specify these values:

+

+* `default`: Use the value specified by the Docker daemon's `--exec-opt` . If the `daemon` does not specify an isolation technology, Microsoft Windows uses `process` as its default value.

+* `process`: Namespace isolation only.

+* `hyperv`: Hyper-V hypervisor partition-based isolation.

+

+Specifying the `--isolation` flag without a value is the same as setting `--isolation="default"`.

+

+### Dealing with dynamically created devices (--device-cgroup-rule)

+

+Devices available to a container are assigned at creation time. The

+assigned devices will both be added to the cgroup.allow file and

+created into the container once it is run. This poses a problem when

+a new device needs to be added to running container.

+

+One of the solution is to add a more permissive rule to a container

+allowing it access to a wider range of devices. For example, supposing

+our container needs access to a character device with major `42` and

+any number of minor number (added as new devices appear), the

+following rule would be added:

+

+```

+docker create --device-cgroup-rule='c 42:* rmw' -name my-container my-image

+```

+

+Then, a user could ask `udev` to execute a script that would `docker exec my-container mknod newDevX c 42 <minor>`

+the required device when it is added.

+

+NOTE: initially present devices still need to be explicitely added to

+the create/run command

@@ -6,7 +6,7 @@ any point.

 The initial status of the container created with **docker create** is 'created'.

-# OPTIONS 

+### OPTIONS 

 The `CONTAINER-DIR` must be an absolute path such as `/src/docs`. The `HOST-DIR`

 can be an absolute path or a `name` value. A `name` value must start with an

@@ -82,18 +82,3 @@ change propagation properties of source mount. Say `/` is source mount for

 To disable automatic copying of data from the container path to the volume, use

 the `nocopy` flag. The `nocopy` flag can be set on bind mounts and named volumes.

-

-# EXAMPLES

-

-## Specify isolation technology for container (--isolation)

-

-This option is useful in situations where you are running Docker containers on

-Windows. The `--isolation=<value>` option sets a container's isolation

-technology. On Linux, the only supported is the `default` option which uses

-Linux namespaces. On Microsoft Windows, you can specify these values:

-

-* `default`: Use the value specified by the Docker daemon's `--exec-opt` . If the `daemon` does not specify an isolation technology, Microsoft Windows uses `process` as its default value.

-* `process`: Namespace isolation only.

-* `hyperv`: Hyper-V hypervisor partition-based isolation.

-

-Specifying the `--isolation` flag without a value is the same as setting `--isolation="default"`.