Help with clearing this up

[MoldyTaint]

I love Proxmox and does super well for what it is, even though I'm a bit still newbie with it. Before this I had an Ubuntu Server + Docker and while it did what it did I was finding myself wanting to learn and explore more. Proxmox and the LXC/VM's were great for that.

For this LXC, when I go and get the IP address through "ip addr" I notice a lot more than normal. I see that there is not only the normal 'lo" and "eth", but the docker ones too which are "br" and "docker", what is new for me now are these that start with Veth. When I look online I see different forums like this from proxmox and this also. While I understand it has something to do with linking/binding of ip addresses and interfaces, aside from that I just don't have much of a clue. Are there some other docs or something that may have a better explanation?

Thank you for your time.

 

[Chris]

Hi,
virtual ethernet devices allow to connect trough different network namespaces, therefore allowing to connect the containers isolated network namespace with the host. See the man page for a good explanation https://man7.org/linux/man-pages/man4/veth.4.html

 

[MoldyTaint]

Hi,
virtual ethernet devices allow to connect trough different network namespaces, therefore allowing to connect the containers isolated network namespace with the host. See the man page for a good explanation https://man7.org/linux/man-pages/man4/veth.4.html

Chris, Thank you so much for the reply and link to the man pages! I think I understand it a bit more fully.

If I'm not mistaken, because I have 4 docker containers running + the docker itself, those usually have a "br" next to them, because it's ALSO in a LXC it also has a "veth" which connects and pulls the LXC's IP address also?

I apologize if these are simple or dumb questions. I do really enjoy the product and hope to get to a better knowledge level with it.

 

[Chris]

Well afaik also docker will create veth interfaces to create tunnels for the docker container network namespaces with (in this particular case) the LXC network namespace. That is why you will have the bridge, so the veth interfaces can be briged to connect the networks to each other, maybe this helps for your understanding https://docs.docker.com/engine/tutorials/networkingcontainers/