debian template creates non-working jessie containers

[ghost]

jessie has systemd by default. the default jessie containers created with the debian template don't work with systemd. you need at least to set lxc.autodev=1 and lxc.kmsg=0 in the config.

[danielkza]

I can confirm I'm running into issues as well, seems to be just a matter of creating per-release overrides for jessie and sid with the correct configurations.

[tpo]

If you add lxc.autodev=1 and lxc.kmsg=0 to the config as you mentioned above, then will the user be able to switch between systemd and non-systemd inits or not?

[tpo]

See also the proposed patch to the template https://lists.linuxcontainers.org/pipermail/lxc-devel/2014-November/010893.html and discussion, and related Debian bugs: https://bugs.debian.org/766233, https://bugs.debian.org/761197 and ttps://bugs.debian.org/766216

[stgraber]

This should have been resolved recently with a change to lxc-debian.

There's still more ongoing work to get systemd to work properly in lxc though (especially unprivileged containers).

[tpo]

I think @stgraber is referring to commit a9bf60b

[stgraber]

Correct

[CameronNemo]

@stgraber are there any negatives to having lxc.autodev = 1 if the init is not systemd?

[stgraber]

The most obvious problem at the moment is that lxc.autodev doesn't work with unprivileged containers. But once we've got the autodev rework done (as is currently being discussed on the mailing-list), there shouldn't be any reason not to make it a default.

The main reason someone would want it off then is if they need a specific configuration for /dev which needs to be persistent across reboots.

[CameronNemo]

Oh, I see. I am trying to adjust the previously mentioned commit to make it easier to reconfigure for systemd in the guest when the guest originally had another init system, and when/if you make autodev the default it will be pretty much down to "comment out this line in getty@.service, add lxc.kmsg = 0 to your lxc config".