-
Notifications
You must be signed in to change notification settings - Fork 670
use nsenter
instead of ip netns exec
#458
Comments
It would seem that
Compared to when the symlink is in place:
|
Bizarrely, if I run it locally with
|
Context:
|
Perhaps the netlink call in question is looking in the process table for the container PID if |
Appears to be failing at https://github.com/torvalds/linux/blob/v3.16/net/core/net_namespace.c#L373 (ESRCH is No such process) |
Ahhh, it's also possible to pass a |
Replace `ip netns exec` with `nsenter` Closes #458.
By replacing our use of
ip netns exec
withnsenter
we could remove the current network namespace symlinking hack.The only downside is that
nsenter
is a fairly recent command. So, for example, it only appeared in Ubuntu 14.10. This is less of an issue post #388 though.The text was updated successfully, but these errors were encountered: