You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The response of ListContainersAsync sometimes contains for a single port binding multiple public host ports. In this case, a service behind the mapped port is not available. It looks like setting the port binding host port to null (assign random port) breaks it. I attached a reproducible example above. E.g. L:89 throws: System.InvalidOperationException: 49196,52481.
Output of
dotnet --info
:What version of Docker.DotNet?:
Steps to reproduce the issue:
What actually happened?:
The response of
ListContainersAsync
sometimes contains for a single port binding multiple public host ports. In this case, a service behind the mapped port is not available. It looks like setting the port binding host port tonull
(assign random port) breaks it. I attached a reproducible example above. E.g.L:89
throws:System.InvalidOperationException: 49196,52481
.... new[] { new PortBinding { HostPort = null } }
: fails... new[] { new PortBinding { HostPort = "0" } }
: successfulThis also breaks
InspectContainerAsync
. In this case the response (list of port bindings) is empty for at least the first call.What did you expect to happen?:
A consistent response.
Additional information:
-
The text was updated successfully, but these errors were encountered: