Know issue?  lxc-fedora command/script missing?  when doing...

# yum install lxc

no command/script is added called 'lxc-fedora'

I untared the 0.7.5 and 0.8.0rc2 tars, and there is a template script
file... lxc-fedora.in in both.  So what gives?

Also, a lot of the LXC documentation, blogs, etc is very dated.  Including
the official LXC web page.  Is someone going to update for Fedora 17?  Most
of the references in Google are over 2 years old now.

Last, has febootstrap been depreciated for use with LXC?  This seems to be a
point of confusion given the dated information and the few blog comments out
on the internet.

Schorschi

-----Original Message-----
From: Stéphane Graber [mailto:stgra...@ubuntu.com] 
Sent: Saturday, July 14, 2012 08:30
To: Serge Hallyn
Cc: Lxc-users@lists.sourceforge.net
Subject: Re: [Lxc-users] lxcbr0 on Ubuntu 12.04

On 07/14/2012 09:48 AM, Serge Hallyn wrote:
> Quoting Clemens Perz (cp...@gmx.net):
>>
>>
>> On 13.07.2012 17:08, Stéphane Graber wrote:
>>> On 07/13/2012 03:36 AM, groupie wrote:
>>>> Hi all!
>>>>
>>>> I tried to figure out a glitch with the bridge interface in 
>>>> precise. Its a fresh desktop install and after booting the machine,
lxcbr0 never exists.
>>>>
>>>> I open a terminal and do sudo service lxc restart and woop, without 
>>>> errors, it just comes up.
>>>>
>>>> Two more details: I dont have any containers in auto, I start them 
>>>> as needed. And there is a named running for local dns resolution on 
>>>> all virtual networks (using kde and vmware on the same machine)
>>>>
>>>> Any ideas where to tweak?
>>>>
>>>> Cheers,
>>>> Your groupie
>>>
>>> You'll probably want to check /var/log/upstart/lxc* for errors.
>>>
>>>
>>
>> That contained a hint indeed:
>> dnsmasq: failed to create listening socket for 192.168.122.1: Address 
>> already in use
>>
>> A look into lxc-net.conf shows that it buggers out when it cant start 
>> dnsmasq and removes the bridge completely. So at starttime named is 
>> some milliseconds faster to aquire the bridge interface and makes 
>> dnsmasq fail. Bridge removed, named kicked in the ass. So you do a 
>> restart later everything works fine.
>>
>> I just added USE_LXC_DNSMASQ="false" to the lxc defaults and the 
>> corresponding if statement to lxc-net.conf. Works now even on boot time.
>>
>> Cheers,
>> Groupie
> 
> Note that the fix for this (installing an /etc/dnsmasq.d/lxc file 
> which makes the system-wide dnsmasq bind-interfaces except lxcbr0) 
> should be clearing SRU soon.  (I thouhgt it already had)
> 
> -serge

It did. It was part of the last batch (0.7.5-3ubuntu59).

--
Stéphane Graber
Ubuntu developer
http://www.ubuntu.com





------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Lxc-users mailing list
Lxc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/lxc-users

Reply via email to