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

Hello everyone, I have encountered a problem with a systemd-nspawn container and deboostrap running in this container. When I try to launch deboostrap inside the container, debootstrap stops because it tries to unpack a tar archive that creates devices like /dev/console. The error is "EPERM".

Re: [systemd-devel] Additional error details when resource limits are exceeded

Hi, Type=simple cannot detect when a service is ready. Systemd simply of teamviewerd but with service inter-dependencies this becomes important. Type=simple considers the service up immediatly thus triggering dependent service for immediate execution while Type=forking considers the service up

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

On Wed, 23.12.15 14:10, Emmanuel Coirier (ecoir...@olfeo.com) wrote: > Hello everyone, > > I have encountered a problem with a systemd-nspawn container and deboostrap > running in this container. > > When I try to launch deboostrap inside the container, debootstrap > stops because it tries to

Re: [systemd-devel] Additional error details when resource limits are exceeded

On Wed, Dec 23, 2015 at 04:07:16PM +0100, Kai Krakow wrote: > Am Wed, 23 Dec 2015 22:55:13 +0800 > schrieb Peter Hoeg : > > > >So, Type=forking is the only way to have synchronization points > > >between service that depend on each other. > > > > In all fairness, the presence of

Re: [systemd-devel] Query regarding "EnvironmentFile"

On Wed, 23.12.15 10:32, Reindl Harald (h.rei...@thelounge.net) wrote: > > > Am 23.12.2015 um 07:01 schrieb Jóhann B. Guðmundsson: > >On 12/23/2015 12:43 AM, Lennart Poettering wrote: > >>Just to clarify that. I think EnvironmentFile= was a mistake, and I > >>explained why. But then again, I am

Re: [systemd-devel] Query regarding "EnvironmentFile"

On Wed, 23.12.15 02:44, Reindl Harald (h.rei...@thelounge.net) wrote: > > > Am 23.12.2015 um 01:24 schrieb Lennart Poettering: > >On Thu, 10.12.15 16:20, Reindl Harald (h.rei...@thelounge.net) wrote: > >> > >>Am 10.12.2015 um 15:46 schrieb Jóhann B. Guðmundsson: > >>>If you are unaware of any

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

On Wed, Dec 23, 2015 at 3:10 PM, Emmanuel Coirier wrote: > Hello everyone, > > I have encountered a problem with a systemd-nspawn container and > deboostrap running in this container. > > When I try to launch deboostrap inside the container, debootstrap stops > because it

Re: [systemd-devel] Query regarding "EnvironmentFile"

On Wed, 23.12.15 06:01, Jóhann B. Guðmundsson (johan...@gmail.com) wrote: > > > On 12/23/2015 12:43 AM, Lennart Poettering wrote: > >Just to clarify that. I think EnvironmentFile= was a mistake, and I > >explained why. But then again, I am not planning to remove it, and I > >never suggested

Re: [systemd-devel] Additional error details when resource limits are exceeded

Am Wed, 23 Dec 2015 22:55:13 +0800 schrieb Peter Hoeg : > Hi, > > >Type=simple cannot detect when a service is ready. Systemd simply > >of teamviewerd but with service inter-dependencies this becomes > >important. > > > >Type=simple considers the service up immediatly thus

Re: [systemd-devel] Query regarding "EnvironmentFile"

On 12/23, Lennart Poettering wrote: > On Wed, 23.12.15 06:01, Jóhann B. Guðmundsson (johan...@gmail.com) wrote: > > What usescases do you see for it's existence. > > Well, the usecase that this is what's out there right now, and we have > to stay compatible. It's not precisely an exotic feature,

Re: [systemd-devel] Query regarding "EnvironmentFile"

On 12/23, Jóhann B. Guðmundsson wrote: > The usual underlying cause of usage of Environment or EnvironmentFile in > type units is more or less always due to the fact that the > daemon/service cannot read configuration file on startup thus the answer > is you would use a daemon that was written

Re: [systemd-devel] journalctl --list-boots fails

On Wed, Oct 14, 2015 at 10:34 AM, Lennart Poettering wrote: > On Wed, 14.10.15 18:18, Lars Noschinski (nosch...@in.tum.de) wrote: > >> On 14.10.2015 17:33, Lennart Poettering wrote: >> > On Thu, 08.10.15 13:04, Lars Noschinski (nosch...@in.tum.de) wrote: >> >> [please CC

Re: [systemd-devel] Query regarding "EnvironmentFile"

24.12.2015 03:48, Alex Crawford пишет: > On 12/23, Jóhann B. Guðmundsson wrote: >> The usual underlying cause of usage of Environment or EnvironmentFile in >> type units is more or less always due to the fact that the >> daemon/service cannot read configuration file on startup thus the answer

Re: [systemd-devel] Query regarding "EnvironmentFile"

Am 23.12.2015 um 21:12 schrieb Jóhann B. Guðmundsson: On 12/23/2015 07:30 PM, Alex Crawford wrote: I like this model and I'm not sure how I would solve this if EnvironmentFile didn't exist. The usual underlying cause of usage of Environment or EnvironmentFile in type units is more or less

Re: [systemd-devel] Query regarding "EnvironmentFile"

Am 23.12.2015 um 23:08 schrieb Jóhann B. Guðmundsson: On 12/23/2015 08:18 PM, Reindl Harald wrote: Am 23.12.2015 um 21:12 schrieb Jóhann B. Guðmundsson: On 12/23/2015 07:30 PM, Alex Crawford wrote: I like this model and I'm not sure how I would solve this if EnvironmentFile didn't

Re: [systemd-devel] nspawn --private-users and setuid

On Fri, 11.12.15 11:36, Leroy Pubel (lepu...@gmail.com) wrote: > Is it considered safe to setuid on a root-owned binary that launches > systemd-nspawn with the argument "--private-users=1000:1"? Well, that all depends on your code... Note that SUID binaries generally have the problem that they

Re: [systemd-devel] Query regarding "EnvironmentFile"

On Wed, 23.12.15 11:30, Alex Crawford (alex.crawf...@coreos.com) wrote: > On 12/23, Lennart Poettering wrote: > > On Wed, 23.12.15 06:01, Jóhann B. Guðmundsson (johan...@gmail.com) wrote: > > > What usescases do you see for it's existence. > > > > Well, the usecase that this is what's out there

Re: [systemd-devel] How to debug machinectl shell?

On Tue, 22.12.15 00:13, Tobias Hunger (tobias.hun...@gmail.com) wrote: > Hello List, > > I am running on arch-linux, using systemd 228 and have a machine > started using systemd-nspawn. It shows up in machinectl list. I can > machinectl login MACHINE into this machine, but when I try to run >

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

On Wed, 23.12.15 23:12, Johan Ouwerkerk (jm.ouwerk...@gmail.com) wrote: > > My goal is to have a light container able to build a software that runs in > > a light container (actually in a legacy chroot). And one of the first steps > > is to debootstrap a virgin system. Is this use case possible

Re: [systemd-devel] Query regarding "EnvironmentFile"

On 12/23/2015 07:48 PM, Lennart Poettering wrote: I see no reason why systemd should be involved with this. Just make etcd a proper daemon, and read its config data directly, rather then serializing it into the command line. In sys v initscript it started out as variable options, placed on

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

> My goal is to have a light container able to build a software that runs in a > light container (actually in a legacy chroot). And one of the first steps is > to debootstrap a virgin system. Is this use case possible ? Maybe try --variant=fakechroot ? Haven't tested this but my guess is that

Re: [systemd-devel] Query regarding "EnvironmentFile"

Am 23.12.2015 um 07:01 schrieb Jóhann B. Guðmundsson: On 12/23/2015 12:43 AM, Lennart Poettering wrote: Just to clarify that. I think EnvironmentFile= was a mistake, and I explained why. But then again, I am not planning to remove it, and I never suggested that. What usescases do you see