On Mon, 2013-09-30 at 23:10 +0200, Tamas Papp wrote: > On 09/30/2013 08:37 PM, Michael H. Warfield wrote: > > Oh? I thought it did, but you had to have the rpm and yum packages > > installed (you won't with the new one). I thought I had tested that out > > on one of my Ubuntu systems. > > This is the end of the process: > > Copy /var/cache/lxc/fedora/x86_64/18/rootfs to /tank/lxc/ipa12/rootfs ... > Copying rootfs to /tank/lxc/ipa12/rootfs ...setting root passwd to root > installing fedora-release package > warning: Failed to read auxiliary vector, /proc not mounted? > warning: Failed to read auxiliary vector, /proc not mounted? > warning: Failed to read auxiliary vector, /proc not mounted? > warning: Failed to read auxiliary vector, /proc not mounted? > warning: Failed to read auxiliary vector, /proc not mounted? > warning: Failed to read auxiliary vector, /proc not mounted? > warning: Failed to read auxiliary vector, /proc not mounted? > warning: Failed to read auxiliary vector, /proc not mounted? > Error: Cannot retrieve metalink for repository: fedora/18/x86_64. Please > verify its path and try again > container rootfs and config created
Oh! /me picks jaw up off the floor laughing. Yeah, that's all fixed. First off, those warnings are just noise. It's because /proc was not mounted in the chrooted space. It has the purpose of reading alternate archs as in i686 under x86_64 for newer versions of rpm. That's harmless but I've FIXED that noise anyways in the new one. The "Error: Cannot retrieve metalink for repository:" is something even more amusing I ran into and I don't really understand why it wasn't showing up more but... It's because a "yum update" is being done chrooted into the cache but /etc/resolv.conf had never been initialized from the host. Consequently, from both of those (and a couple of others), I've been mounting proc, copying /etc/resolv.conf, and bind mounting /dev into the chrooted namespaces to avoid a lot of problems. Life seems to have gotten more complicated from when this was originally written. :-P Regards, Mike > But I wouldn't care about this if you rewrite it anyway. > BTW: > ii lxc > 1.0.0~alpha1.0+master~201309 > amd64 Linux Containers userspace tools > > > I also suggest you to take a look at this: > > https://github.com/lxc/lxc/issues/47 > > > Sorry about the quality of the report, it was quite late, when I wrote it:) > > > Cheers, > tamas > -- Michael H. Warfield (AI4NB) | (770) 985-6132 | m...@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!
signature.asc
Description: This is a digitally signed message part
------------------------------------------------------------------------------ October Webinars: Code for Performance Free Intel webinars can help you accelerate application performance. Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from the latest Intel processors and coprocessors. See abstracts and register > http://pubads.g.doubleclick.net/gampad/clk?id=60134791&iu=/4140/ostg.clktrk
_______________________________________________ Lxc-users mailing list Lxc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/lxc-users
