From b2b90e5bb39f9e0d6898cf5c499985bcd9e8ccc1 Mon Sep 17 00:00:00 2001
From: Guillaume Lours <705411+glours@users.noreply.github.com>
Date: Tue, 29 Jul 2025 15:01:22 +0200
Subject: [PATCH] remove extensions and limitations section from extends
 documentation

Signed-off-by: Guillaume Lours <705411+glours@users.noreply.github.com>
---
 .../how-tos/multiple-compose-files/extends.md      | 14 --------------
 1 file changed, 14 deletions(-)

diff --git a/content/manuals/compose/how-tos/multiple-compose-files/extends.md b/content/manuals/compose/how-tos/multiple-compose-files/extends.md
index 5380c555b2e..d2dccccbc51 100644
--- a/content/manuals/compose/how-tos/multiple-compose-files/extends.md
+++ b/content/manuals/compose/how-tos/multiple-compose-files/extends.md
@@ -157,20 +157,6 @@ services:
       - queue
 ```
 
-## Exceptions and limitations
-
-`volumes_from` and `depends_on` are never shared between services using
-`extends`. These exceptions exist to avoid implicit dependencies; you always
-define `volumes_from` locally. This ensures dependencies between services are
-clearly visible when reading the current file. Defining these locally also
-ensures that changes to the referenced file don't break anything.
-
-`extends` is useful if you only need a single service to be shared and you are
-familiar with the file you're extending to, so you can tweak the
-configuration. But this isn’t an acceptable solution when you want to re-use
-someone else's unfamiliar configurations and you don’t know about its own
-dependencies.
-
 ## Relative paths
 
 When using `extends` with a `file` attribute which points to another folder, relative paths