Fixes documentation for swift driver "container" parameter
No longer claims that an additional segments container is used Signed-off-by: Brian Bland <brian.bland@docker.com>
This commit is contained in:
parent
4946d0d035
commit
90fe4b9256
1 changed files with 2 additions and 5 deletions
|
@ -49,10 +49,7 @@ An implementation of the `storagedriver.StorageDriver` interface that uses [Open
|
||||||
</td>
|
</td>
|
||||||
<td>
|
<td>
|
||||||
<p>
|
<p>
|
||||||
The name of your Swift container where you wish to store objects. An
|
The name of your Swift container where you wish to store objects. The driver creates the named container during its initialization.
|
||||||
additional container called <code><container>_segments</code> stores the data
|
|
||||||
is used. The driver creates both the named container and the segments
|
|
||||||
container during its initialization.
|
|
||||||
</p>
|
</p>
|
||||||
</td>
|
</td>
|
||||||
</tr>
|
</tr>
|
||||||
|
|
Loading…
Reference in a new issue