Search results

It seemed to work with the bare lxc commands. There are no instructions how to use this to make a new template.

That's the whole point. Many packages these days depend on systemd. So what is your suggestion: blacklist those packages?

Ok, so we'll have to do with a broken jessie template until some 3rd party comes up with a solution? Will wait patiently then ..

So, can we expect a jessie template that includes systemd?

You mean like a good wine?

So, this is apparently not actually the case. I just built a plain lxc with jessie and systemd (or at least systemctl) works just fine (using: lxc-create -n container -t debian -- -r jessie). Other topics on the issue also seem to say that in most cases jessie with systemd should work inside...

Why not, if I may ask? I've already run in to a number of situations where packages were depending on it. How would one build a jessie template that uses it? I noticed I cannot install dab. and the sourcecode of dab shows indeed that sysvinit is enforced (commit...

Using the debian-8.0-standard template systemctl gives: 'Failed to get D-Bus connection: Unknown error -1' It seems that systemd isn't actually running inside the container. Is this a problem with the template or do you need to add some extra settings? I've also looked in to lxc-systemd...