jasder
/
runc
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

bundle.md: clarify arbitrary/conventional dirnames 

Add a note describing that the names of directories in the bundle are
arbitrary and referenced from the configuration, but conventional names
(like "rootfs" and "signatures") should be used.
This commit is contained in:
Jonathan Boulle 2015-07-02 17:50:49 -07:00
parent 91f5ad7cfa
commit 112dcbb6a9
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
bundle.md
View File

@ -16,7 +16,7 @@ A Standard Container bundle is a directory containing all the content needed to
The syntax and semantics for `config.json` are described in [this specification](config.md).
One or more *content directories* may be adjacent to the configuration file. This must include at least the root filesystem (referenced in the configuration file by the *root* field) and may include other related content (signatures, other configs, etc.). The interpretation of these resources is specified in the configuration.
One or more *content directories* may be adjacent to the configuration file. This must include at least the root filesystem (referenced in the configuration file by the *root* field) and may include other related content (signatures, other configs, etc.). The interpretation of these resources is specified in the configuration. The names of the directories may be arbitrary, but users should consider using conventional names as in the example below.
```
/
@ -25,6 +25,6 @@ One or more *content directories* may be adjacent to the configuration file. Thi
!
--- rootfs
!
--- sigs
--- signatures
```