[Lxc-users] [systemd-devel] Unable to run systemd in an LXC / cgroup container.

[John]

On 26/10/12 22:02, Michael H. Warfield wrote:
> On Fri, 2012-10-26 at 12:11 -0400, Michael H. Warfield wrote:
>> On Thu, 2012-10-25 at 23:38 +0200, Lennart Poettering wrote:
>>> On Thu, 25.10.12 11:59, Michael H. Warfield (mhw at WittsEnd.com) wrote:
>>>> I SUSPECT the hang condition is something to do with systemd trying to
>>>> start and interactive console on /dev/console, which sysvinit and
>>>> upstart do not do.
>>> Yes, this is documented, please see the link I already posted, and which
>>> I linked above a second time.
>> This may have been my fault.  I was using the -o option to lxc-start
>> (output logfile) and failed to specify the -c (console output redirect)
>> option.  It seems to fire up nicely (albeit with other problems) with
>> that additional option.  Continuing my research.
> Confirming.  Using the -c option for the console file works.
> Unfortunately, thanks to no getty's on the ttys so lxc-console does not
> work and no way to connect to that console redirect and the failure of
> the network to start, I'm still trying to figure out just what is face
> planting in a container I can not access.  :-/=/  Punch out the punch
> list one PUNCH at at time here.
>
>>>> I've got some more problems relating to shutting down containers, some
>>>> of which may be related to mounting tmpfs on /run to which /var/run is
>>>> symlinked to.  We're doing halt / restart detection by monitoring utmp
>>>> in that directory but it looks like utmp isn't even in that directory
>>>> anymore and mounting tmpfs on it was always problematical.  We may have
>>>> to have a more generic method to detect when a container has shut down
>>>> or is restarting in that case.
>>> I can't parse this. The system call reboot() is virtualized for
>>> containers just fine and the container managaer (i.e. LXC) can check for
>>> that easily.
>> Apparently, in recent kernels, we can.  Unfortunately, I'm still finding
>> that I can not restart a container I have previously halted.  I have no
>> problem with sysvinit and upstart systems on this host, so it is a
>> container problem peculiar to systemd containers.  Continuing to
>> research that problem.
>>
>>> Lennart
>>> -- 
>>> Lennart Poettering - Red Hat, Inc.
>> Regards,
>> Mike
>
>
> ------------------------------------------------------------------------------
> WINDOWS 8 is here.
> Millions of people.  Your app in 30 days.
> Visit The Windows 8 Center at Sourceforge for all your go to resources.
> http://windows8center.sourceforge.net/
> join-generation-app-and-make-money-coding-fast/
>
>
> _______________________________________________
> Lxc-users mailing list
> Lxc-users at lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/lxc-users
I raised the question about LXC/systemd a while back and have been 
trying to follow the conversation but I have to admit it's going 
somewhat over my head. I've also been away on another piece of work but 
would now like to understand where things lie with LXC and systemd 
inside a container.

I have just updated my system to 0.8.0 and I can't see any changes to 
make a systemd container work. Are there changes in 0.8.0 ?

If so, I'd be grateful for some guidance on what I need to do to to my 
configuration to make it work.

I'm also happy to help test this if I can. If it helps I am on Arch Linux.

many thanks everyone.

John

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxcontainers.org/pipermail/lxc-users/attachments/20121204/59b93712/attachment.html>