Replies: 1 comment
-
https://github.com/rootless-containers/slirp4netns#motivation It creates a TAP device inside a network namespace. Outside the sandbox it can bind to a specific address.
Any namespace is ephemeral. Nothing stops you from automating the process.
It should be already possible with |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Description
For this exact purpose I wrote a script.
https://github.com/planetoryd/netns-proxy/
Also to demonstrate what my need is.
I'm still not sure what slirp4netns does under the hood or how should I use it.
So, configure and spawning tun2socks+dnsproxy for each process' netns I think ?
IDK. It doesn't sound very elegant. Process netnses are ephemeral. It means I have to call my tool each time I launch my app ?
However this feature is implemented, I'd like some official-ish support for socks5-proxied NetNSes, or custom netns in general (along with the long requested sandbox having netns with VPN TUNs)
Beta Was this translation helpful? Give feedback.
All reactions