@@ -215,7 +215,7 @@ build:
215
215
> In your Dockerfile, if you specify `ARG` before the `FROM` instruction,
216
216
> `ARG` is not available in the build instructions under `FROM`.
217
217
> If you need an argument to be available in both places, also specify it under
218
- > the `FROM` instruction. Refer to the [understand how ARGS and FROM interact](/engine/reference/builder.md#understand-how-arg-and-from-interact)
218
+ > the `FROM` instruction. Refer to the [understand how ARGS and FROM interact](../.. /engine/reference/builder.md#understand-how-arg-and-from-interact)
219
219
> section in the documentation for usage details.
220
220
221
221
You can omit the value when specifying a build argument, in which case its value
@@ -271,7 +271,7 @@ An entry with the ip address and hostname is created in `/etc/hosts` inside cont
271
271
Specify a build’s container isolation technology. On Linux, the only supported value
272
272
is `default`. On Windows, acceptable values are `default`, `process` and
273
273
` hyperv` . Refer to the
274
- [Docker Engine docs](/engine/reference/commandline/run.md#specify-isolation-technology-for-container---isolation)
274
+ [Docker Engine docs](../.. /engine/reference/commandline/run.md#specify-isolation-technology-for-container---isolation)
275
275
for details.
276
276
277
277
If unspecified, Compose will use the `isolation` value found in the service's definition
@@ -281,7 +281,7 @@ to determine the value to use for builds.
281
281
282
282
> Added in [version 2.1](compose-versioning.md#version-21) file format
283
283
284
- Add metadata to the resulting image using [Docker labels](/config/labels-custom-metadata.md).
284
+ Add metadata to the resulting image using [Docker labels](../.. /config/labels-custom-metadata.md).
285
285
You can use either an array or a dictionary.
286
286
287
287
It's recommended that you use reverse-DNS notation to prevent your labels from
@@ -357,7 +357,7 @@ build:
357
357
> Added in [version 2.3](compose-versioning.md#version-23) file format
358
358
359
359
Build the specified stage as defined inside the `Dockerfile`. See the
360
- [multi-stage build docs](/develop/develop-images/multistage-build.md) for
360
+ [multi-stage build docs](../.. /develop/develop-images/multistage-build.md) for
361
361
details.
362
362
363
363
` ` ` yaml
@@ -397,7 +397,7 @@ command: bundle exec thin -p 3000
397
397
` ` `
398
398
399
399
The command can also be a list, in a manner similar to
400
- [dockerfile](/engine/reference/builder.md#cmd):
400
+ [dockerfile](../.. /engine/reference/builder.md#cmd):
401
401
402
402
` ` ` yaml
403
403
command: ["bundle", "exec", "thin", "-p", "3000"]
@@ -490,7 +490,7 @@ services:
490
490
>
491
491
> `depends_on` does not wait for `db` and `redis` to be "ready" before
492
492
> starting `web` - only until they have been started. If you need to wait
493
- > for a service to be ready, see [Controlling startup order](/compose /startup-order.md)
493
+ > for a service to be ready, see [Controlling startup order](.. /startup-order.md)
494
494
> for more on this problem and strategies for solving it.
495
495
496
496
> Added in [version 2.1](compose-versioning.md#version-21) file format.
@@ -572,7 +572,7 @@ entrypoint: /code/entrypoint.sh
572
572
` ` `
573
573
574
574
The entrypoint can also be a list, in a manner similar to
575
- [dockerfile](/engine/reference/builder.md#entrypoint):
575
+ [dockerfile](../.. /engine/reference/builder.md#entrypoint):
576
576
577
577
` ` ` yaml
578
578
entrypoint: ["php", "-d", "memory_limit=-1", "vendor/bin/phpunit"]
@@ -728,7 +728,7 @@ indefinitely. Compose does not support circular references and `docker-compose`
728
728
returns an error if it encounters one.
729
729
730
730
For more on `extends`, see the
731
- [the extends documentation](/compose /extends.md#extending-services).
731
+ [the extends documentation](.. /extends.md#extending-services).
732
732
733
733
# ## external_links
734
734
@@ -776,7 +776,7 @@ host system to be added. An example of where this is useful is when multiple
776
776
containers (running as different users) need to all read or write the same
777
777
file on the host system. That file can be owned by a group shared by all the
778
778
containers, and specified in `group_add`. See the
779
- [Docker documentation](/engine/reference/run.md#additional-groups) for more
779
+ [Docker documentation](../.. /engine/reference/run.md#additional-groups) for more
780
780
details.
781
781
782
782
A full example :
@@ -800,7 +800,7 @@ used.
800
800
801
801
Configure a check that's run to determine whether or not containers for this
802
802
service are "healthy". See the docs for the
803
- [HEALTHCHECK Dockerfile instruction](/engine/reference/builder.md#healthcheck)
803
+ [HEALTHCHECK Dockerfile instruction](../.. /engine/reference/builder.md#healthcheck)
804
804
for details on how healthchecks work.
805
805
806
806
` ` ` yaml
@@ -889,7 +889,7 @@ services:
889
889
> The default init binary that is used is [Tini](https://github.com/krallin/tini),
890
890
> and is installed in `/usr/libexec/docker-init` on the daemon host. You can
891
891
> configure the daemon to use a custom init binary through the
892
- > [`init-path` configuration option](/engine/reference/commandline/dockerd.md#daemon-configuration-file).
892
+ > [`init-path` configuration option](../.. /engine/reference/commandline/dockerd.md#daemon-configuration-file).
893
893
894
894
# ## isolation
895
895
@@ -898,12 +898,12 @@ services:
898
898
Specify a container’s isolation technology. On Linux, the only supported value
899
899
is `default`. On Windows, acceptable values are `default`, `process` and
900
900
` hyperv` . Refer to the
901
- [Docker Engine docs](/engine/reference/commandline/run.md#specify-isolation-technology-for-container---isolation)
901
+ [Docker Engine docs](../.. /engine/reference/commandline/run.md#specify-isolation-technology-for-container---isolation)
902
902
for details.
903
903
904
904
# ## labels
905
905
906
- Add metadata to containers using [Docker labels](/config/labels-custom-metadata.md). You can use either an array or a dictionary.
906
+ Add metadata to containers using [Docker labels](../.. /config/labels-custom-metadata.md). You can use either an array or a dictionary.
907
907
908
908
It's recommended that you use reverse-DNS notation to prevent your labels from conflicting with those used by other software.
909
909
@@ -942,7 +942,7 @@ the alias, or the service name if no alias was specified.
942
942
943
943
Links are not required to enable services to communicate - by default,
944
944
any service can reach any other service at that service’s name. (See also, the
945
- [Links topic in Networking in Compose](/compose /networking.md#links).)
945
+ [Links topic in Networking in Compose](.. /networking.md#links).)
946
946
947
947
Links also express dependency between services in the same way as
948
948
[depends_on](#depends_on), so they determine the order of service startup.
@@ -966,7 +966,7 @@ logging:
966
966
967
967
The `driver` name specifies a logging driver for the service's
968
968
containers, as with the ``--log-driver`` option for docker run
969
- ([documented here](/config/containers/logging/configure.md)).
969
+ ([documented here](../.. /config/containers/logging/configure.md)).
970
970
971
971
The default value is json-file.
972
972
@@ -1296,7 +1296,7 @@ web:
1296
1296
Specify the default number of containers to deploy for this service. Whenever
1297
1297
you run `docker-compose up`, Compose creates or removes containers to match
1298
1298
the specified number. This value can be overridden using the
1299
- [`--scale`](/compose /reference/up.md) flag.
1299
+ [`--scale`](.. /reference/up.md) flag.
1300
1300
1301
1301
` ` ` yaml
1302
1302
web:
@@ -1497,7 +1497,7 @@ volumes:
1497
1497
> When creating bind mounts, using the long syntax requires the
1498
1498
> referenced folder to be created beforehand. Using the short syntax
1499
1499
> creates the folder on the fly if it doesn't exist.
1500
- > See the [bind mounts documentation](/storage/bind-mounts.md#differences-between--v-and---mount-behavior)
1500
+ > See the [bind mounts documentation](../.. /storage/bind-mounts.md#differences-between--v-and---mount-behavior)
1501
1501
> for more information.
1502
1502
1503
1503
# ## volume\_driver
@@ -1518,7 +1518,7 @@ volume_driver: mydriver
1518
1518
> entry in the [top-level `volumes` option](#volume-configuration-reference).
1519
1519
1520
1520
1521
- See [Docker Volumes](/storage/volumes.md) and
1521
+ See [Docker Volumes](../.. /storage/volumes.md) and
1522
1522
[Volume Plugins](/engine/extend/plugins_volume/) for more information.
1523
1523
1524
1524
# ## volumes_from
@@ -1568,7 +1568,7 @@ restart: unless-stopped
1568
1568
# ## cpu_count, cpu_percent, cpu\_shares, cpu\_period, cpu\_quota, cpus, cpuset, domainname, hostname, ipc, mac\_address, mem\_limit, memswap\_limit, mem\_swappiness, mem\_reservation, oom_kill_disable, oom_score_adj, privileged, read\_only, shm\_size, stdin\_open, tty, user, working\_dir
1569
1569
1570
1570
Each of these is a single value, analogous to its
1571
- [docker run](/engine/reference/run.md#runtime-constraints-on-resources) counterpart.
1571
+ [docker run](../.. /engine/reference/run.md#runtime-constraints-on-resources) counterpart.
1572
1572
1573
1573
> Added in [version 2.2](compose-versioning.md#version-22) file format.
1574
1574
>
@@ -1646,10 +1646,10 @@ While it is possible to declare [volumes](#volumes) on the fly as part of the
1646
1646
service declaration, this section allows you to create named volumes that can be
1647
1647
reused across multiple services (without relying on `volumes_from`), and are
1648
1648
easily retrieved and inspected using the docker command line or API.
1649
- See the [docker volume](/engine/reference/commandline/volume_create.md)
1649
+ See the [docker volume](../.. /engine/reference/commandline/volume_create.md)
1650
1650
subcommand documentation for more information.
1651
1651
1652
- See [use volumes](/storage/volumes.md) and [volume plugins](/engine/extend/plugins_volume/)
1652
+ See [use volumes](../.. /storage/volumes.md) and [volume plugins](/engine/extend/plugins_volume/)
1653
1653
for general information on volumes.
1654
1654
1655
1655
Here's an example of a two-service setup where a database's data directory is
@@ -1752,7 +1752,7 @@ volumes:
1752
1752
> Added in [version 2.1](compose-versioning.md#version-21) file format.
1753
1753
1754
1754
Add metadata to containers using
1755
- [Docker labels](/config/labels-custom-metadata.md). You can use either
1755
+ [Docker labels](../.. /config/labels-custom-metadata.md). You can use either
1756
1756
an array or a dictionary.
1757
1757
1758
1758
It's recommended that you use reverse-DNS notation to prevent your labels from
@@ -1801,7 +1801,7 @@ volumes:
1801
1801
1802
1802
The top-level `networks` key lets you specify networks to be created. For a full
1803
1803
explanation of Compose's use of Docker networking features, see the
1804
- [Networking guide](/compose /networking.md).
1804
+ [Networking guide](.. /networking.md).
1805
1805
1806
1806
# ## driver
1807
1807
@@ -1885,7 +1885,7 @@ you can set this option to `true`.
1885
1885
> Added in [version 2.1](compose-versioning.md#version-21) file format.
1886
1886
1887
1887
Add metadata to containers using
1888
- [Docker labels](/config/labels-custom-metadata.md). You can use either
1888
+ [Docker labels](../.. /config/labels-custom-metadata.md). You can use either
1889
1889
an array or a dictionary.
1890
1890
1891
1891
It's recommended that you use reverse-DNS notation to prevent your labels from
@@ -1991,8 +1991,8 @@ networks:
1991
1991
1992
1992
# # Compose documentation
1993
1993
1994
- - [User guide](/compose /index.md)
1995
- - [Installing Compose](/compose /install.md)
1994
+ - [User guide](.. /index.md)
1995
+ - [Installing Compose](.. /install.md)
1996
1996
- [Compose file versions and upgrading](compose-versioning.md)
1997
- - [Samples](/samples/index.md)
1998
- - [Command line reference](/compose /reference/index.md)
1997
+ - [Samples](../.. /samples/index.md)
1998
+ - [Command line reference](.. /reference/index.md)
0 commit comments