[lxc-users] Fedory 20 LXC fails to start on Ubuntu 14.04 host?

[Michael H. Warfield]

On Mon, 2014-05-26 at 10:58 -0400, Michael H. Warfield wrote:
> On Mon, 2014-05-26 at 14:18 +0700, Fajar A. Nugraha wrote:
> > On Mon, May 26, 2014 at 2:03 PM, Timotheus Pokorra
> > <timotheus at pokorra.de> wrote:
> >         Hello Federico,
> >         that is strange.
> >         I tried now on my old Laptop which runs Ubuntu 14.04, and got
> >         the same error:
> >         <30>systemd[1]: Listening on /dev/initctl Compatibility Named
> >         Pipe.
> >         <30>systemd[1]: Starting Root Slice.
> >         <27>systemd[1]: Caught <SEGV>, dumped core as pid 11.
> >         <30>systemd[1]: Freezing execution.
> >         
> >         
> >         my kernel is:
> >         uname -a
> >         Linux timotheusp-LIFEBOOK-S7110 3.13.0-24-generic #47-Ubuntu
> >         SMP Fri
> >         May 2 23:31:42 UTC 2014 i686 i686 i686 GNU/Linux
> >         
> >         I am also using the packages 1.0.3-0ubuntu3 of lxc.
> >         
> >         What might be the difference, so that it works for you and
> >         does not work for me?
> >         
> > 
> > 
> > 
> > 
> > Try https://www.mail-archive.com/lxc-users@lists.linuxcontainers.org/msg00993.html

> > Look for "unconfined".

> Oh!  The AppArmour profile thing.  Palm / forehead / slap.  Yeah.

In that other thread, Serge and I were discussion if we might just set
that option and it would be ignored on hosts such as Fedora, CentOS, and
Oracle which don't use AppArmour.  I just tested that and it does appear
to be the case.  I'll probably change the template for the Fedora and
CentOS containers to default to specifying that option.

Regards,
Mike
 
> 
> > 
> >         >>>> The LXC host (Ubuntu) is a virtual machine running in a
> >         XEN environment.
> >         >>>> I would understand if that is not possible, but it is
> >         possible since
> >         >>>> Debian 7 and CentOS 6 containers run fine on this host.
> >         >>>
> >         >>> XEN???
> >         >>>
> >         >>> Oh crap...  It's information like this that is critical to
> >         understand
> >         >>> what's going on.
> >         >>>
> >         >>> You're in an environment with a Fedora 20 container
> >         running on an Ubuntu
> >         >>> virtualized host in a Xen guest running under a Xen
> >         paravirtualization
> >         >>> hypervisor.  Without knowing this, it would be impossible
> >         to even guess
> >         >>> where the problem may lay (even with this information, it
> >         may be
> >         >>> impossible).  I haven't even begun to attempt to reproduce
> >         it but the
> >         >>> number of independent variables just shot through the
> >         roof.
> >         >>>
> >         >>> First order of troubleshooting.  Eliminate independent
> >         variables...
> >         
> > 
> > 
> > 
> > 
> > Try running fedora under lxc under xen under vmware :P
> > 
> > 
> > FWIW though, when using standard configurations (e.g. distro-bundled
> > kernel, or vanilla upstream kernel with distro-provided config), xen
> > usually behaves similar-enough to bare-metal for most cases. It's only
> > when someone uses their own stripped-down custom-config-and-build
> > kernel that results might vary wildly.
> > 
> > 
> > -- 
> > Fajar
> > 
> 
> 

-- 
Michael H. Warfield (AI4NB) | (770) 978-7061 |  mhw at WittsEnd.com
   /\/\|=mhw=|\/\/          | (678) 463-0932 |  http://www.wittsend.com/mhw/
   NIC whois: MHW9          | An optimist believes we live in the best of all
 PGP Key: 0x674627FF        | possible worlds.  A pessimist is sure of it!

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 482 bytes
Desc: This is a digitally signed message part
URL: <http://lists.linuxcontainers.org/pipermail/lxc-users/attachments/20140526/9d92d79b/attachment.sig>