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
If VPP forwarder and VPP are located in different containers, they cannot share /proc/1/fd/x.
Forwarder performs API requests to VPP with file describing Client/Endpoint net NS, currently it is /proc/1/fd/x received from recvfd - it is not accessible from VPP container and such request fails.
Possible solution
Add netns chain elements creating named net NS and replacing netNSURL in kernel mechanism before Requesting/Closing kernel chain element.
@Bolodya1997 For Calico/VPP integration, run in the host:pid space for the forwarder. The VPP plugin is also running in host:pid for Calico/VPP, and Calico/VPP itself passes to VPP things in /proc/${pid}/... so we know this works in host:pid
Parent issue
networkservicemesh/integration-k8s-kind#325
Issue
If VPP forwarder and VPP are located in different containers, they cannot share
/proc/1/fd/x
.Forwarder performs API requests to VPP with file describing Client/Endpoint net NS, currently it is
/proc/1/fd/x
received fromrecvfd
- it is not accessible from VPP container and such request fails.Possible solution
Add
netns
chain elements creating named net NS and replacingnetNSURL
in kernel mechanism before Requesting/Closingkernel
chain element.common.go
server.go
client.go
The text was updated successfully, but these errors were encountered: