Toerless Eckert <Toerless.Eckert@xxxxxxxxxxxxxxxxxxxxxxxxxx> writes: > THanks for replying, > > Sorry for asking what probably are a lot of naive questions, my excuse is > that the documentation is somewhat scattered/incomplete ? ;-)) > > I am trying to figure out how to minimize the virtualization to just the network > name space and instantiate it in a lightweight fashion that can easily > be counterfitted into some existing system. > > What i would like to have is some simple program like "run-ns XXXX <program> <args>" > that would run program <args> within namespace XXXX. > > So i was looking for some system call like set_ns(XXXX), but it seems there > is no API like that. Instead i guess i would need to have a "server" process > with pid XXXX that does an unshare(CLONE_NEWNS) and then listens for requests > to fork client programs, and run-ns would need to send a request to that XXXX > process to fork off <program> <args> and make sure that it can transfer all > the pre-existing context of run-ns like pid/gid(s), cwd, environment, and i don't > even know all the other context a linux process has these days. And then of course > communicate exit status of <program> back from XXXX to run-ns. > > Meaning: it's great to have something like network name spaces, but without > some setns(XXXX) system call, it's really difficult to use these network name > spaces outside of a concept like LXC - which is a shame, because otherwise > the nework name space woudl exactly be what i am looking for. Definitely old docs. ip netns add ip netns delete ip netns exec And yes there is a setns system call. If you don't have that you have old bits. All of that should be merged and documented. Eric _______________________________________________ Containers mailing list Containers@xxxxxxxxxxxxxxxxxxxxxxxxxx https://lists.linuxfoundation.org/mailman/listinfo/containers
