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
Today's implementation assumes that at least one side of every VETH pair remains assigned to the host namespace. I.e., it is not possible to create setups like the following, where the db<--->client VETH pair between the web and postgres containers:
.-----------. .----------.
| web | | postgres |
web '--wan--db--' '--client--'
'------' '---------'
Expected Behavior
Internal VETH pairs between containers should be allowed.
Steps To Reproduce
No response
Additional information
This limitation exists because of how confd skips the setup for container interfaces in netdag_gen_iface():
Current Behavior
Today's implementation assumes that at least one side of every VETH pair remains assigned to the host namespace. I.e., it is not possible to create setups like the following, where the
db<--->client
VETH pair between theweb
andpostgres
containers:Expected Behavior
Internal VETH pairs between containers should be allowed.
Steps To Reproduce
No response
Additional information
This limitation exists because of how
confd
skips the setup for container interfaces innetdag_gen_iface()
:infix/src/confd/src/ietf-interfaces.c
Lines 529 to 534 in d3bfbb5
If this branch is taken for both sides, then no one will actually create the pair.
The text was updated successfully, but these errors were encountered: