Skip to content

Commit b2b90e5

Browse files
committed
remove extensions and limitations section from extends documentation
Signed-off-by: Guillaume Lours <[email protected]>
1 parent 19c02b4 commit b2b90e5

File tree

1 file changed

+0
-14
lines changed
  • content/manuals/compose/how-tos/multiple-compose-files

1 file changed

+0
-14
lines changed

content/manuals/compose/how-tos/multiple-compose-files/extends.md

Lines changed: 0 additions & 14 deletions
Original file line numberDiff line numberDiff line change
@@ -157,20 +157,6 @@ services:
157157
- queue
158158
```
159159

160-
## Exceptions and limitations
161-
162-
`volumes_from` and `depends_on` are never shared between services using
163-
`extends`. These exceptions exist to avoid implicit dependencies; you always
164-
define `volumes_from` locally. This ensures dependencies between services are
165-
clearly visible when reading the current file. Defining these locally also
166-
ensures that changes to the referenced file don't break anything.
167-
168-
`extends` is useful if you only need a single service to be shared and you are
169-
familiar with the file you're extending to, so you can tweak the
170-
configuration. But this isn’t an acceptable solution when you want to re-use
171-
someone else's unfamiliar configurations and you don’t know about its own
172-
dependencies.
173-
174160
## Relative paths
175161

176162
When using `extends` with a `file` attribute which points to another folder, relative paths

0 commit comments

Comments
 (0)