mirror of https://github.com/docker/cli.git
docs: build: fix minor markdown and syntax issues
Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
This commit is contained in:
parent
68cad50f61
commit
7d4ae13753
|
@ -99,16 +99,16 @@ $ docker build https://github.com/docker/rootfs.git#container:docker
|
||||||
The following table represents all the valid suffixes with their build
|
The following table represents all the valid suffixes with their build
|
||||||
contexts:
|
contexts:
|
||||||
|
|
||||||
Build Syntax Suffix | Commit Used | Build Context Used
|
| Build Syntax Suffix | Commit Used | Build Context Used |
|
||||||
--------------------------------|-----------------------|-------------------
|
|--------------------------------|-----------------------|--------------------|
|
||||||
`myrepo.git` | `refs/heads/master` | `/`
|
| `myrepo.git` | `refs/heads/master` | `/` |
|
||||||
`myrepo.git#mytag` | `refs/tags/mytag` | `/`
|
| `myrepo.git#mytag` | `refs/tags/mytag` | `/` |
|
||||||
`myrepo.git#mybranch` | `refs/heads/mybranch` | `/`
|
| `myrepo.git#mybranch` | `refs/heads/mybranch` | `/` |
|
||||||
`myrepo.git#pull/42/head` | `refs/pull/42/head` | `/`
|
| `myrepo.git#pull/42/head` | `refs/pull/42/head` | `/` |
|
||||||
`myrepo.git#:myfolder` | `refs/heads/master` | `/myfolder`
|
| `myrepo.git#:myfolder` | `refs/heads/master` | `/myfolder` |
|
||||||
`myrepo.git#master:myfolder` | `refs/heads/master` | `/myfolder`
|
| `myrepo.git#master:myfolder` | `refs/heads/master` | `/myfolder` |
|
||||||
`myrepo.git#mytag:myfolder` | `refs/tags/mytag` | `/myfolder`
|
| `myrepo.git#mytag:myfolder` | `refs/tags/mytag` | `/myfolder` |
|
||||||
`myrepo.git#mybranch:myfolder` | `refs/heads/mybranch` | `/myfolder`
|
| `myrepo.git#mybranch:myfolder` | `refs/heads/mybranch` | `/myfolder` |
|
||||||
|
|
||||||
### Tarball contexts
|
### Tarball contexts
|
||||||
|
|
||||||
|
@ -455,11 +455,11 @@ technology. On Linux, the only supported is the `default` option which uses
|
||||||
Linux namespaces. On Microsoft Windows, you can specify these values:
|
Linux namespaces. On Microsoft Windows, you can specify these values:
|
||||||
|
|
||||||
|
|
||||||
| Value | Description |
|
| Value | Description |
|
||||||
|-----------|---------------------------------------------------------------------------------------------------------------------------------------------------------------|
|
|-----------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
|
||||||
| `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. |
|
| `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. |
|
| `process` | Namespace isolation only. |
|
||||||
| `hyperv` | Hyper-V hypervisor partition-based isolation. |
|
| `hyperv` | Hyper-V hypervisor partition-based isolation. |
|
||||||
|
|
||||||
Specifying the `--isolation` flag without a value is the same as setting `--isolation="default"`.
|
Specifying the `--isolation` flag without a value is the same as setting `--isolation="default"`.
|
||||||
|
|
||||||
|
@ -479,10 +479,10 @@ image. Commands after the target stage will be skipped.
|
||||||
|
|
||||||
```dockerfile
|
```dockerfile
|
||||||
FROM debian AS build-env
|
FROM debian AS build-env
|
||||||
...
|
# ...
|
||||||
|
|
||||||
FROM alpine AS production-env
|
FROM alpine AS production-env
|
||||||
...
|
# ...
|
||||||
```
|
```
|
||||||
|
|
||||||
```console
|
```console
|
||||||
|
|
Loading…
Reference in New Issue