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
Is your feature request related to a problem? Please describe.
When running a Rails app that uses the better_errors gem, the gem needs to be given this range in the config in order for it to display when running under Docker, as otherwise it will only work on localhost.
I can't get this information through lazydocker, though: when I select a network in the left pane, it shows the network config on the right, but does not show the IP range assigned to the network — I need to run docker network inspect networkname outside of lazydocker to find that out.
Describe the solution you'd like
The information is available at IPAM.Config.Subnet, and could be displayed in the config pane when a network is selected. (The gateway might be useful to some people, too, though it's not needed in my case…)
Describe alternatives you've considered
Manually running docker network inspect networkname and picking through the output to find what I need. That's not very lazy, though 😁
Additional context
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
When running a Rails app that uses the
better_errors
gem, the gem needs to be given this range in the config in order for it to display when running under Docker, as otherwise it will only work on localhost.I can't get this information through lazydocker, though: when I select a network in the left pane, it shows the network config on the right, but does not show the IP range assigned to the network — I need to run
docker network inspect networkname
outside of lazydocker to find that out.Describe the solution you'd like
The information is available at
IPAM.Config.Subnet
, and could be displayed in the config pane when a network is selected. (The gateway might be useful to some people, too, though it's not needed in my case…)Describe alternatives you've considered
Manually running
docker network inspect networkname
and picking through the output to find what I need. That's not very lazy, though 😁Additional context
The text was updated successfully, but these errors were encountered: