Open tailhook opened 6 years ago
@tailhook , thank you for pointing out your work (vagga looks awesome. I'll definitely give it a try).
Do you consider making the netlink/bridge creation part a separate crate/library?
I'm wondering if promoting this upstream in pnetlink would be a better idea since I've already borrowed a decent amount of code from pnetlink. Besides that, I mostly dig through official netlink documentation / API reference.
How vagga deals with networking?
I'm wondering if promoting this upstream in pnetlink would be a better idea since I've already borrowed a decent amount of code from pnetlink.
Well, this will help too, but I'd like something more high level.
How vagga deals with networking?
Usually it uses host network namespace (because other ways need elevated privileges, and because it allows easier interoperability with running processes locally). But there is a network testing mode, briefly described here: http://vagga.readthedocs.io/en/latest/network.html
Hi!
I'm also building container runtime in rust (vagga and lithos). I'm very interested in using what you have done here for creating bridge. The reason I've not done it myself is laking documentation for it (did you find any, by the way?).
Do you consider making the netlink/bridge creation part a separate crate/library?
I also maintain unshare and libmount crates for containers, that you might find useful.