[Lxc-users] Unable to create lxc CT on fedora 19
Michael H. Warfield
mhw at WittsEnd.com
Mon Jul 8 16:54:55 UTC 2013
On Mon, 2013-07-08 at 08:51 -0700, jjs - mainphrame wrote:
> Hi Michael,
> Yes, it is lxc-0.8 from the repos. I did notice that ubuntu shipped
> with lxc-0.9.
> You're right, f19 failed during the download phase. All the others
> failed at the end with the chroot error.
Good. I just completed Ubuntu and Debian container installs without
running into any errors (though the Ubuntu container install seemed to
take FOREVER).
I'm working on a patch for the Fedora template and will submit it up to
the devel list, hopefull later today (I have several things on my list).
Once Serge and Stéphane accept that, it'll be in the git repo for the
next release.
> Thanks for the feedback, I now have a better sense of what's going on.
> If you'd care to share any of your packages or scripts, I'd be
> indebted.
I'll see what I can do.
Thomas Moschny posted a link to some prebuilt rpms here:
http://thm.fedorapeople.org/lxc/
I haven't used them but I suspect they're not much different than the
ones I build. You may need to manually removed the lxc-doc package from
the stock repository as there's a conflict in the rpm builds and the
0.9.0 package is not obsoleting the Fedora 0.8.0 lxc-doc package.
> Joe
Regards,
Mike
>
> On Mon, Jul 8, 2013 at 7:05 AM, Michael H. Warfield <mhw at wittsend.com>
> wrote:
> On Sat, 2013-07-06 at 16:11 -0700, jjs - mainphrame wrote:
> > All,
> >
> >
> > Noob question here. I've been testing lxc on ubunbtu 13.04
> and
> > everything just works. However, all my attempts to create an
> lxc CT on
> > fedora 19 have failed.
>
>
> > The result is the same when attempting to create debian,
> ubuntu or
> > fedora containers. What am I missing here?
>
>
> As it so happens, I just upgraded one of my F18 workstations
> to F19 over
> the weekend and had not gotten around to testing this yet. So
> I just
> tested. Spotted an immediate and obvious problem before I
> even started
> and fixed that before even making the attempt.
>
> 1) What version of lxc are you running?
>
> The stock lxc rpms from the repos are 0.8.0. Uh, oh. No,
> that's not
> gonna work at all. Version 0.8.0 is not compatible with the
> version of
> systemd that's shipped with F19 (or F18 for that matter). You
> need to
> upgrade lxc to at least 0.9.0 (current) and that's been
> discussed in
> several other threads. There are some prebuilt rpms floating
> around,
> though I typically build my own since I've done some work on
> the
> binaries and the Fedora template. I would highly recommend
> installing
> from some prebuilt rpms (or building your own) rather than
> from source
> "compile and install".
>
> No for testing...
>
> 2) The lxc-fedora template (even in 0.9.0) is busted, as I
> feared it
> would be, for Fedora 19 because the Fedora 19 release file is
> a -2
> release and it's only looking for a -1 release. I saw that
> code a month
> ago and thought "that can't be right" but it hasn't busted
> until now.
> Nobody answered when I asked about that logic on the devel
> list back
> then so I guess it's one more thing on my list to fix. The
> whole retry
> logic in that template is wrong, IMNSHO.
>
> 3) The errors couldn't be "the same" because the template
> logic is
> different. No where in the Fedora template do we do a
> "chroot .*
> mount.*proc". In fact, we don't even mount proc (which may be
> something
> else I should look into). That error on the "chroot ... mount
> -t proc"
> would have never shown up in an fedora create (but you would
> have blown
> up for the release download).
>
> 4) After installing lxc-0.9.0 on my F19 system AND hacking the
> bloody
> lxc-fedora template for the release extension, I was able to
> successfully install an F19 container on an F19 host. I'll
> try Ubuntu
> and Debian next.
>
> AFAICT, almost none of the other templates have allowed for
> cross distro
> container creation, which sucks. One more thing to work on.
> :-P
>
> Regards,
> Mike
>
> > --- output follows ---
> >
> >
> > [root at max ~]# lxc-create -n debian1 -t debian
> > /usr/share/lxc/templates/lxc-debian
> > is /usr/share/lxc/templates/lxc-debian
> > debootstrap is /sbin/debootstrap
> >
> > Checking cache download
> > in /var/cache/lxc/debian/rootfs-squeeze-amd64 ...
> > Downloading debian minimal ...
> > I: Retrieving Release
> > W: Cannot check Release signature; keyring file not
> > available /usr/share/keyrings/debian-archive-keyring.gpg
> > I: Retrieving Packages
> > I: Validating Packages
> > I: Resolving dependencies of required packages...
> > I: Resolving dependencies of base packages...
> > I: Found additional required dependencies: insserv
> libbz2-1.0 libdb4.8
> > libslang2
> >
> >
> > ... <snipped> ...
> >
> >
> > I: Extracting mount...
> > I: Extracting util-linux...
> > I: Extracting liblzma2...
> > I: Extracting xz-utils...
> > I: Extracting zlib1g...
> > W: Failure trying to run:
> > chroot /var/cache/lxc/debian/partial-squeeze-amd64 mount -t
> proc
> > proc /proc
> > W:
> >
> See /var/cache/lxc/debian/partial-squeeze-amd64/debootstrap/debootstrap.log for details
> > Failed to download the rootfs, aborting.
> > Failed to download 'debian base'
> > failed to install debian
> > lxc-create: failed to execute template 'debian'
> > lxc-create: aborted
> > [root at max ~]#
> >
> >
> >
--
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/20130708/374b080c/attachment.pgp>
More information about the lxc-users
mailing list