On Thu, Oct 24, 2013 at 10:29:10PM +0200, Zbigniew Jędrzejewski-Szmek wrote: > On Thu, Oct 24, 2013 at 12:13:34PM -0700, Steve Langasek wrote: > > And this is not just an issue because of people not wanting to use systemd > > init, but also because systemd init *can't* run in a container. > Whoah, that's not true: > sudo systemd-nspawn -bD ~/images/fedora-19 > works just fine :) My understanding, which may be based on dated information, is that systemd-nspawn doesn't fully contain the system in the way most others (e.g. users of lxc) talk about when they speak of containers: MAC, cgroups support inside the container, and possibly other things. If you use lxc-start instead of systemd-nspawn, does your Fedora image work? Last I knew, the answer was "no". -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. Ubuntu Developer http://www.debian.org/ slangasek@ubuntu.com vorlon@debian.org
Attachment:
signature.asc
Description: Digital signature