Make LXC container discovery a thing #170
cryptochrome
started this conversation in
Ideas
Replies: 1 comment 1 reply
-
|
Definitely on my radar! Here's an issue tracking the enhancement for when I get around to it. Getting into the LXC > veth > bridge thing you said, It sounds like you're anticipating a dependency of sorts between information from the proxmox scan and docker scan that means it would be best to run Proxmox first, is that right? Can you explain a bit further becasue I want to make sure I understand how it should fit together to accomplish what you're envisioning. |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
I would love to see Netvisor support full discovery and mapping out of LXC environments - similar to what it already does with Docker. Meaning: Discover LXC exists, scan for containers and associated bridges and veth interfaces and put them into the topology.
Example:
Let's say you have a hots that runs both Docker and LXC, and you'll end up with potentially hundreds of veth interfaces, dozens of bridges, all webbed together (or not). It would be great if this "web" could be visualized as a topology. LXC container > veth > bridge.
Hope this makes sense.
Beta Was this translation helpful? Give feedback.
All reactions