github/linuxkit
1
0
Fork 0
mirror of https://github.com/linuxkit/linuxkit.git synced 2025-10-31 05:12:03 +00:00
Code Issues Projects Releases Wiki Activity

docs: Update documentation regarding private repos

Browse Source 
Signed-off-by: Rolf Neugebauer <rolf.neugebauer@docker.com>
This commit is contained in:
Rolf Neugebauer
2018-07-20 13:29:07 +01:00
parent 04c061fb8c
commit 5dcb3d48cb
1 changed files with 6 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

7
docs/yaml.md
View File

@@ -1,6 +1,6 @@
# Configuration Reference # Configuration Reference
The `moby` tool assembles a set of containerised components into in image. The simplest The `linuxkit build` command assembles a set of containerised components into in image. The simplest
type of image is just a `tar` file of the contents (useful for debugging) but more useful type of image is just a `tar` file of the contents (useful for debugging) but more useful
outputs add a `Dockerfile` to build a container, or build a full disk image that can be outputs add a `Dockerfile` to build a container, or build a full disk image that can be
booted as a linuxKit VM. The main use case is to build an assembly that includes booted as a linuxKit VM. The main use case is to build an assembly that includes
@@ -10,6 +10,11 @@ The yaml configuration specifies the components used to build up an image . All
are downloaded at build time to create an image. The image is self-contained and immutable, are downloaded at build time to create an image. The image is self-contained and immutable,
so it can be tested reliably for continuous delivery. so it can be tested reliably for continuous delivery.
Components are specified as Docker images which are pulled from a registry during build if they
are not available locally. The Docker images are optionally verified with Docker Content Trust.
For private registries or private repositories on a registry credentials provided via
`docker login` are re-used.
The configuration file is processed in the order `kernel`, `init`, `onboot`, `onshutdown`, The configuration file is processed in the order `kernel`, `init`, `onboot`, `onshutdown`,
`services`, `files`. Each section adds files to the root file system. Sections may be omitted. `services`, `files`. Each section adds files to the root file system. Sections may be omitted.