Dockge stack does not show containers that are incorporated into the compose file using "include"

[adamadavidson]

⚠️ Please verify that this bug has NOT been reported before.

• I checked and didn't find similar issue

🛡️ Security Policy

• I agree to have read this project Security Policy

Description

When creating a compose-yaml file for a stack using the "include" element, Dockge does not show any containers that are not in the base compose.yaml.

So, if I have one container in the compose.yaml file but 3 further containers added to the stack using the "include" element, Dockge only shows the one container.

I appreciate this may be more of a feature request than a bug.

👟 Reproduction steps

1. Create compose.yaml
2. Add include element to pull in additional containers from other compose files.

👀 Expected behavior

See 4 containers in Dockge

😓 Actual Behavior

Only 1 container is shown in Dockge

Dockge Version

1.3.3

💻 Operating System and Arch

Ubuntu 22.04

🌐 Browser

Microsoft Edge Version 120.0.2210.61

🐋 Docker Version

Docker 24.0.7

🟩 NodeJS Version

No response

📝 Relevant log output

No response

[codersaur]

Better support for the include element would be great all round. I define all my networks in a common docker-networks.yaml file which I include in each project stack, but Dockge wants to add an empty networks: {} element instead.

[Wigsinator]

I've started doing the same. Dockge really doesn't play nice with it, the networks list ends up full of blank elements. I'd really appreciate it if Dockge had better support for stacks spread across multiple files.

[ChrisonSimtian]

just started migrating to Dockge and ran into exactly this.
Would be nice to see this feature implemented, as it helps to make bigger stacks a bit easier to structure