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).
Original GitHub issue: https://github.com/moghtech/komodo/issues/217
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 2026-05-12 20:57:05 -05:00
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.
<!-- gh-comment-id:2533761611 -->
@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.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @mattsmallman on GitHub (Dec 10, 2024).
Original GitHub issue: https://github.com/moghtech/komodo/issues/217
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.
@mbecker20 commented on GitHub (Dec 11, 2024):
This is a bug, I didn't consider the
mergingof services when working with multiple files.I do have the solution in mind, re #189 it will first use
docker compose configto 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.@mattsmallman commented on GitHub (Apr 1, 2025):
Seems to be fixed in 1.17 🎉 🙏