Re: [systemd-devel] mknod forbidden in systemd-nspawn container

2015-12-28 Thread Johan Ouwerkerk
On Mon, Dec 28, 2015 at 4:29 PM, Emmanuel Coirier wrote: > > I'll look at multistrap. It let you customize device creation. It should then > be possible to customize it to not create any device... > Multistrap doesn't do 'device node' creation at all. It uses APT to download packages to a direct

Re: [systemd-devel] mknod forbidden in systemd-nspawn container

2015-12-28 Thread Emmanuel Coirier
> Johan Ouwerkerk [mailto:jm.ouwerk...@gmail.com] > Maybe try --variant=fakechroot ? Already tested : it still create those devices. The debootstrap script doesn't have any option to disable devices creation or ignore errors produced by this operation. I've tried with appending "|| tue" to the

Re: [systemd-devel] systemctl enable myunit.service ---> Failed to execute operation: Invalid argument

2015-12-28 Thread bobafetthotmail
On 12/28/2015 04:55 AM, Andrei Borzenkov wrote: 27.12.2015 22:23, bobafetthotmail пишет: I'm still trying to understand why my unit (see the quote below) that calls a script can be started/stopped but cannot be enabled.. I tried changing everything in the unit, it still fails any help? I

Re: [systemd-devel] mknod forbidden in systemd-nspawn container

2015-12-28 Thread Emmanuel Coirier
Thanks for your answer, but... > Mantas Mikulėnas [mailto:somewhere] > Hmm, isn't debootstrap supposed to run outside the container? Or are you > trying to nest two containers? It's indeed a nested container. The outer container is a working container in which I do all I need to do. The inner c

Re: [systemd-devel] echo message not coming on terminal with systemd

2015-12-28 Thread Navneet Sinha
On Fri, Dec 18, 2015 at 6:10 AM, Navneet Sinha wrote: > I have systemd service, say xyzWarmup.service. > > Here is the service file > > [Unit] > Description=Xyz agent. > After=fooAfter.service > Before=fooBefore1.service > Before=fooBefore2.service > > [Service] > # Du