mirror of
https://github.com/fosrl/pangolin.git
synced 2026-05-21 01:11:38 -05:00
[GH-ISSUE #847] Selecting a container in the "View Docker Containers" modal does not apply the port #10425
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/pangolin#10425
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @absynth42 on GitHub (Jun 5, 2025).
Original GitHub issue: https://github.com/fosrl/pangolin/issues/847
When defining a resource via the new Docker socket functionality and opening the "View Docker Containers" modal, you can either click the port(s) or the orange "select" button.
When clicking one of the exposed ports, the IP address and port number are applied to the resource definition correctly.
However, when clicking "select", only the IP address is applied. I would expect that the port is also applied, at least if there's no ambiguity (i.e. the container only exposes one port).
@miloschwartz commented on GitHub (Jun 5, 2025):
To select a port you need to click the port. THis is because a container can more than one port, so you have to choose which to use. I suppose we could automatically pick the first port though.
@absynth42 commented on GitHub (Jun 6, 2025):
In this case, I guess my bug report ist: "The orange select button should be greyed out until one port is selected". Because right now, you can click "select" without doing that and just the IP address is propagated on to the resource definition.
The best workflow would be: Make the user select a port first, then make the "Select" button clickable. Maybe have a tutorial wizard as soon as users first open the modal.
@ahmaddxb commented on GitHub (Jun 16, 2025):
When you click the port, it works, but it would be better to use the container name rather than the IP, as this could change.
@github-actions[bot] commented on GitHub (Jul 1, 2025):
This issue has been automatically marked as stale due to 14 days of inactivity. It will be closed in 14 days if no further activity occurs.
@github-actions[bot] commented on GitHub (Jul 16, 2025):
This issue has been automatically closed due to inactivity. If you believe this is still relevant, please open a new issue with up-to-date information.