[Lxc-users] Issues in using lxc in Fedora 14

[Michael H. Warfield]

On Tue, 2013-07-30 at 16:02 +0530, Ajith Adapa wrote: 
> Hi,

> I am stuck with a issue in Fedora 14 using lxc.

Stuck?  Stuck with what?  Stuck with an issue or stuck with Fedora 14.
Using Fedora 14 as a host at this point in time is insane.  It's way
over a year and a half past EOL - end of life (F16 is already EOL) - and
I've already shotgunned all my Fedora 14 hosts and guests.  You won't
even get high risk security fixes and updates for F14 at this point.
You're just engaging in an unsupportable exercise in masochism.  You
won't have recent kernels and you won't have recent versions of lxc
which will never become available for that version of Fedora from the
repositories.

> I have create a container using the template available at -
> https://launchpadlibrarian.net/83751818/lxc-fedora

> container is created successfuly and when I try lxc-start command I am
> getting stuck as shown below.

> There seems to be some issues with /etc/fstab. Any pointers or proper
> template to create a container would be of great help.

No clue.  I've been working on the Fedora template and patching it.
That template you pointed to is seriously very out of date.  It looks
like the old template I started patching some time ago.  I wouldn't
trust it.  I've added a lot of patches (someone pointed to an up-to-date
cut on github) for a lot of fedora versions.  Still...  I would not
guarantee THAT will work on lxc 0.7.2.  You got bigger problems on both
fronts (Fedora version and LXC version) that you need to fix first.

> # lxc-start -n test
>         Welcome to Fedora 
> Setting hostname localhost:                                [  OK  ]
> Checking filesystems
> WARNING: couldn't open /etc/fstab: No such file or directory
>                                                            [  OK  ]
> warning: can't open /etc/fstab: No such file or directory
> mount: can't find / in /etc/fstab or /etc/mtab
> Mounting local filesystems:  warning: can't open /etc/fstab: No such
> file or directory
>                                                            [  OK  ]
> No such file or directory
> Enabling /etc/fstab swaps:  swapon: /etc/fstab: open failed: No such
> file or directory
>                                                            [FAILED]
> Entering non-interactive startup
> Bringing up loopback interface:                            [  OK  ]
> Bringing up interface eth0:  
> Determining IP information for eth0... done.
>                                                            [  OK  ]
> Starting system logger:                                    [  OK  ]
> awk: cmd. line:1: fatal: cannot open file `/etc/fstab' for reading (No
> such file or directory)
> awk: cmd. line:1: fatal: cannot open file `/etc/fstab' for reading (No
> such file or directory)
> awk: cmd. line:1: fatal: cannot open file `/etc/fstab' for reading (No
> such file or directory)
> awk: cmd. line:1: fatal: cannot open file `/etc/fstab' for reading (No
> such file or directory)
> Mounting other filesystems:  warning: can't open /etc/fstab: No such
> file or directory
>                                                           [  OK  ]
> 
> ^[[17~^C^Z^F[root at localhost ~]# lxc-version 
> lxc version: 0.7.2

That version has to end.  I can't support it and won't even bother to
debug it.  We're at 0.9 and closing in on 1.0.  I have patches for
templates and even base lxc binaries at all those levels.  We can't even
support 0.7.5 while even 0.8 has problems that can only be resolved by
upgrading.  There are rpms available (which will install on Fedora 14 -
I have built and installed similar in parallel).  Upgrade to lxc 0.9.0
FIRST and then try it.  Upgrade to the latest Fedora and then ask...  I
refuse to even test on a Fedora 14 host (which I don't even have any
longer and haven't had for almost a year).  It makes no bloody sense.
If it doesn't work, well, there's your first problem.  I wouldn't even
look at it at this point.  That's got to be fundamental, to your ground
work, to get up-to-date first.

Fedora is nice and rock solid stable and I absolutely love it but it is
intended for those of us who (yes - are batshit crazy and) want and
demand the latest toys and features and have no fear of venturing onto
the bleeding edge of technology.  You accept that burden and
responsibility of upgrading and staying on that edge.  You made that
choice.  If you have to stay at the Fedora 14 level, you should not be
on Fedora at all, you should be on CentOS 6 or similar which has a
longer support and release cycle.  But, then you don't get the nice new
shiny toys we're building here.  Goes with the territory.  You can't
have it both ways.

Sorry if I'm coming across harsh here but Fedora 14 has to be a
non-starter at this point.  It's not worth wasting time here.  You are
on an unsupported version of Fedora using an unsupported version of LXC.
First step...  Get up to date.  I don't have your problem at all.
But...  I'm running F17 on my test host (which is near EOL already) and
F18 on my production engines with an LXC 0.9.0 upgrade.  I don't have
your problem and can not possibly suggest what's wrong with your setup.

Regards,
Mike
-- 
Michael H. Warfield (AI4NB) | (770) 985-6132 |  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/20130731/3b2858e6/attachment.pgp>