On Wed, 10.12.14 13:52, Jan Synacek (jsyna...@redhat.com) wrote:
> Lennart Poettering writes:
> > On Wed, 10.12.14 09:21, Jan Synacek (jsyna...@redhat.com) wrote:
> >
> >> systemd-detect-virt would print "none" when using nspawn to run a shell
> >> inside a container and then running systemd-dete
On Wed, Dec 10, 2014 at 01:52:08PM +0100, Jan Synacek wrote:
> Lennart Poettering writes:
> > On Wed, 10.12.14 09:21, Jan Synacek (jsyna...@redhat.com) wrote:
> >
> >> systemd-detect-virt would print "none" when using nspawn to run a shell
> >> inside a container and then running systemd-detect-vi
Lennart Poettering writes:
> On Wed, 10.12.14 09:21, Jan Synacek (jsyna...@redhat.com) wrote:
>
>> systemd-detect-virt would print "none" when using nspawn to run a shell
>> inside a container and then running systemd-detect-virt in it, because
>> the shell would be PID 1, not the actuall systemd-
On Wed, 10.12.14 09:21, Jan Synacek (jsyna...@redhat.com) wrote:
> systemd-detect-virt would print "none" when using nspawn to run a shell
> inside a container and then running systemd-detect-virt in it, because
> the shell would be PID 1, not the actuall systemd-detect-virt
> process.
So, previo
systemd-detect-virt would print "none" when using nspawn to run a shell
inside a container and then running systemd-detect-virt in it, because
the shell would be PID 1, not the actuall systemd-detect-virt process.
---
src/shared/virt.c | 19 ++-
1 file changed, 6 insertions(+), 13
