Unhealthy Stack when service is defined in multiple compose files #151

New Issue

GiteaMirror · 2025-10-31T15:03:21-05:00

GiteaMirror commented

2025-10-31 15:03:21 -05:00

Originally created by @mattsmallman on GitHub (Dec 10, 2024).

Komodo reports 7 services when only 6 are defined in multiple compose files and reports the stack as unhealthy.

I have a core compose file with dev, test, prod and staging variations configured in separate compose files that are run accordingly. For my prod and staging environments Komodo reports them as being unhealthy despite all the services reporting healthy or being up with no health check. I think this is a result of some form of counting in Komodo as it looks for 7 but only finds 6 services. The services tab shows 7 services although only 6 are defined in the compose files. The duplicate service is defined in the base compose file and modified in the environment specific compose file. The stack startup and run as I would expect.

Originally created by @mattsmallman on GitHub (Dec 10, 2024). Komodo reports 7 services when only 6 are defined in multiple compose files and reports the stack as unhealthy. I have a core compose file with dev, test, prod and staging variations configured in separate compose files that are run accordingly. For my prod and staging environments Komodo reports them as being unhealthy despite all the services reporting healthy or being up with no health check. I think this is a result of some form of counting in Komodo as it looks for 7 but only finds 6 services. The services tab shows 7 services although only 6 are defined in the compose files. The duplicate service is defined in the base compose file and modified in the environment specific compose file. The stack startup and run as I would expect.

GiteaMirror added the bug label 2025-10-31 15:03:21 -05:00

GiteaMirror closed this issue

2025-10-31 15:03:22 -05:00

GiteaMirror commented

2025-10-31 15:03:22 -05:00

@mbecker20 commented on GitHub (Dec 11, 2024):

This is a bug, I didn't consider the merging of services when working with multiple files.

I do have the solution in mind, re #189 it will first use docker compose config to apply all the interpolation / merges, and then extract the services from the result there. This way, Komodo will definitely match the services that docker compose will produce after applying the possible operations.

@mbecker20 commented on GitHub (Dec 11, 2024): This is a bug, I didn't consider the `merging` of services when working with multiple files. I do have the solution in mind, re #189 it will first use `docker compose config` to apply all the interpolation / merges, and then extract the services from the result there. This way, Komodo will definitely match the services that docker compose will produce after applying the possible operations.

GiteaMirror commented

2025-10-31 15:03:23 -05:00

@mattsmallman commented on GitHub (Apr 1, 2025):

Seems to be fixed in 1.17 🎉 🙏

@mattsmallman commented on GitHub (Apr 1, 2025): Seems to be fixed in 1.17 🎉 🙏

GiteaMirror referenced this issue

2025-10-31 15:18:51 -05:00

[PR #151] [MERGED] 1.16.4 #698

Sign in to join this conversation.