Re: [systemd-devel] systemd-nspawn and process spawning using nsenter issue

On Mon, Nov 02, 2015 at 03:36:49PM +, Richard Maw wrote: > > for that? If not is there a kernel interface to create one? > > I don't know of any utilities, but /proc/$pid/ns/net is a symlink pointing > to a magic file that refers to the network namespace. I think about "lsns" command to list

Re: [systemd-devel] systemd-nspawn and process spawning using nsenter issue

On Mon, 02.11.15 20:35, Aliaksei Sheshka (sheshka...@gmail.com) wrote: > > > > Note that all units you join need to have PrivateNetwork=yes set if > > they shall live in the same namespace. Did both your units have this set? > > I have my unit c7-test like that: > >

[systemd-devel] systemd-nspawn and process spawning using nsenter issue

Hello! I have some systemd-nspawn and namespace related question. Assume following commands, $ systemctl start c7-test #starring our container $ systemctl status c7-test #checking if it is running and looking for inside /usr/lib/systemd/systemd process $ nsenter -t 22333 -n

Re: [systemd-devel] systemd-nspawn and process spawning using nsenter issue

On Mon, Nov 02, 2015 at 09:27:42AM -0500, Aliaksei Sheshka wrote: > Hello! > > I have some systemd-nspawn and namespace related question. > Assume following commands, > > $ systemctl start c7-test #starring our container > $ systemctl status c7-test #checking if it is running and looking for >

Re: [systemd-devel] systemd-nspawn and process spawning using nsenter issue

On Mon, 02.11.15 09:27, Aliaksei Sheshka (sheshka...@gmail.com) wrote: > Hello! > > I have some systemd-nspawn and namespace related question. > Assume following commands, > > $ systemctl start c7-test #starring our container > $ systemctl status c7-test #checking if it is running and looking

Re: [systemd-devel] systemd-nspawn and process spawning using nsenter issue

On Mon, Nov 2, 2015 at 1:05 PM, Lennart Poettering wrote: > > BTW: another way to deal with network namespaces in systemd is via > PrivateNetwork=yes and JoinsNamespaceOf=, but I am not whether that > matches what you want to do... Perhaps, I've tried [Unit]

Re: [systemd-devel] systemd-nspawn and process spawning using nsenter issue

On Mon, 02.11.15 14:52, Aliaksei Sheshka (sheshka...@gmail.com) wrote: > On Mon, Nov 2, 2015 at 1:05 PM, Lennart Poettering > wrote: > > > > > > BTW: another way to deal with network namespaces in systemd is via > > PrivateNetwork=yes and JoinsNamespaceOf=, but I am not

Re: [systemd-devel] systemd-nspawn and process spawning using nsenter issue

> > Note that all units you join need to have PrivateNetwork=yes set if > they shall live in the same namespace. Did both your units have this set? I have my unit c7-test like that: ExecStart=/usr/bin/systemd-nspawn --quiet --keep-unit --boot --link-journal=try-guest --network-macvlan=eth0