[Feature Request] More Links #217

New Issue

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

GiteaMirror commented

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

Originally created by @MRobi1 on GitHub (Feb 16, 2025).

I'd love to see more links available in the UI.

One of the things I find I'm missing most from portainer is how it exposed the published ports as clickable links from the containers list.

This would make a great addition to the containers page, the services tab on the stack page and also docker/containers on the server page. The data is all available since the IP is given when selecting server, and port is exposed in the compose file for the stack.

The stacks page has a link to the server

It would be a nice addition if this same section on the server page had links to any stacks/deployments/repos configured under it. I know it's in Resources but this would be nice for quick navigation. Although I can picture some servers having a large number of stacks on them which may require some thought from a UI perspective. Maybe an expandable section if > 2 or 3.

Originally created by @MRobi1 on GitHub (Feb 16, 2025). I'd love to see more links available in the UI. 1) One of the things I find I'm missing most from portainer is how it exposed the published ports as clickable links from the containers list. ![Image](https://github.com/user-attachments/assets/3b268b29-124f-47d8-841a-196b25e727bf) This would make a great addition to the containers page, the services tab on the stack page and also docker/containers on the server page. The data is all available since the IP is given when selecting server, and port is exposed in the compose file for the stack. 2) The stacks page has a link to the server ![Image](https://github.com/user-attachments/assets/e4a49e54-5422-41ba-a28f-bfd1ad87b813) It would be a nice addition if this same section on the server page had links to any stacks/deployments/repos configured under it. I know it's in Resources but this would be nice for quick navigation. Although I can picture some servers having a large number of stacks on them which may require some thought from a UI perspective. Maybe an expandable section if > 2 or 3.

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

GiteaMirror commented

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

@jhedfors commented on GitHub (May 6, 2025):

I can't seem to find a container's published ports anywhere in komodo.

@jhedfors commented on GitHub (May 6, 2025): I can't seem to find a container's published ports anywhere in komodo.

GiteaMirror commented

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

@ramess18 commented on GitHub (May 6, 2025):

I also miss automatically populated clickable links from Portainer. The Links config is only manual as I am aware.

@ramess18 commented on GitHub (May 6, 2025): I also miss automatically populated clickable links from Portainer. The **Links** config is only manual as I am aware.

GiteaMirror commented

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

@mbecker20 commented on GitHub (Aug 27, 2025):

The containers and stack services now feature ports. Noting that Stack header could also use the combined service ports as well as in the service table.

@mbecker20 commented on GitHub (Aug 27, 2025): The containers and stack services now feature ports. Noting that Stack header could also use the combined service ports as well as in the service table.

GiteaMirror referenced this issue

2026-04-11 09:54:26 -05:00

[GH-ISSUE #217] Unhealthy Stack when service is defined in multiple compose files #2030

GiteaMirror referenced this issue

2026-04-13 14:49:24 -05:00

[GH-ISSUE #217] Unhealthy Stack when service is defined in multiple compose files #3175

GiteaMirror referenced this issue

2026-04-21 23:46:56 -05:00

[GH-ISSUE #217] Unhealthy Stack when service is defined in multiple compose files #4749

GiteaMirror referenced this issue

2026-04-24 18:54:24 -05:00

[GH-ISSUE #217] Unhealthy Stack when service is defined in multiple compose files #5920