* Getting started - Error message
@ 2011-03-03 18:55 Philip Rhoades
[not found] ` <4D6FE422.1040807-8eKeQ+h1VH4pAS55Wn97og@public.gmane.org>
0 siblings, 1 reply; 3+ messages in thread
From: Philip Rhoades @ 2011-03-03 18:55 UTC (permalink / raw)
To: containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA
People,
I used this info to get started on Fedora 14 x86_64:
http://www.techrepublic.com/blog/opensource/introducing-linux-virtual-containers-with-lxc/1289
and everything seems happy when doing the setup stuff but when I try to run:
/usr/bin/lxc-execute -n test -f /etc/lxc/lxc-test.conf /bin/bash
I get:
lxc-execute: network is not created for 'lxc.network.link' = 'br0
lxc.network.hwaddr = 4a:49:43:49:79:bd' option
lxc-execute: failed to process 'lxc.network.link = br0
lxc.network.hwaddr = 4a:49:43:49:79:bd
'
lxc-execute: failed to read configuration file
but the conf file is readable:
-rw-r--r-- 1 root root 215 Mar 4 05:29 /etc/lxc/lxc-test.conf
Suggestions?
Thanks,
Phil.
--
Philip Rhoades
GPO Box 3411
Sydney NSW 2001
Australia
E-mail: phil-8eKeQ+h1VH4pAS55Wn97og@public.gmane.org
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: Getting started - Error message
[not found] ` <4D6FE422.1040807-8eKeQ+h1VH4pAS55Wn97og@public.gmane.org>
@ 2011-03-04 8:08 ` Daniel Lezcano
[not found] ` <4D709E19.2090704-GANU6spQydw@public.gmane.org>
0 siblings, 1 reply; 3+ messages in thread
From: Daniel Lezcano @ 2011-03-04 8:08 UTC (permalink / raw)
To: phil-8eKeQ+h1VH4pAS55Wn97og
Cc: containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA
On 03/03/2011 07:55 PM, Philip Rhoades wrote:
> People,
>
> I used this info to get started on Fedora 14 x86_64:
>
> http://www.techrepublic.com/blog/opensource/introducing-linux-virtual-containers-with-lxc/1289
>
> and everything seems happy when doing the setup stuff but when I try to run:
>
> /usr/bin/lxc-execute -n test -f /etc/lxc/lxc-test.conf /bin/bash
>
> I get:
>
> lxc-execute: network is not created for 'lxc.network.link' = 'br0
> lxc.network.hwaddr = 4a:49:43:49:79:bd' option
>
> lxc-execute: failed to process 'lxc.network.link = br0
> lxc.network.hwaddr = 4a:49:43:49:79:bd
> '
> lxc-execute: failed to read configuration file
>
> but the conf file is readable:
>
> -rw-r--r-- 1 root root 215 Mar 4 05:29 /etc/lxc/lxc-test.conf
The blog shows something like that:
"lxc.utsname = test lxc.network.type = veth lxc.network.flags = up
lxc.network.link = br0 lxc.network.hwaddr = 4a:49:43:49:79:bd
lxc.network.ipv4 = 192.168.250.150 lxc.network.ipv6 =
2003:db8:1:0:214:1234:fe0b:3596"
The configuration file should be in this format:
lxc.utsname = test
lxc.network.type = veth
lxc.network.flags = up
lxc.network.link = br0
lxc.network.hwaddr = 4a:49:43:49:79:bd
lxc.network.ipv4 = 192.168.250.150
lxc.network.ipv6 = 2003:db8:1:0:214:1234:fe0b:3596
Thanks
-- Daniel
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: Getting started - Error message
[not found] ` <4D709E19.2090704-GANU6spQydw@public.gmane.org>
@ 2011-03-07 9:23 ` Philip Rhoades
0 siblings, 0 replies; 3+ messages in thread
From: Philip Rhoades @ 2011-03-07 9:23 UTC (permalink / raw)
To: Daniel Lezcano; +Cc: containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA
Daniel,
On 2011-03-04 19:08, Daniel Lezcano wrote:
> On 03/03/2011 07:55 PM, Philip Rhoades wrote:
>> People,
>>
>> I used this info to get started on Fedora 14 x86_64:
>>
>> http://www.techrepublic.com/blog/opensource/introducing-linux-virtual-containers-with-lxc/1289
>>
>>
>> and everything seems happy when doing the setup stuff but when I try
>> to run:
>>
>> /usr/bin/lxc-execute -n test -f /etc/lxc/lxc-test.conf /bin/bash
>>
>> I get:
>>
>> lxc-execute: network is not created for 'lxc.network.link' = 'br0
>> lxc.network.hwaddr = 4a:49:43:49:79:bd' option
>>
>> lxc-execute: failed to process 'lxc.network.link = br0
>> lxc.network.hwaddr = 4a:49:43:49:79:bd
>> '
>> lxc-execute: failed to read configuration file
>>
>> but the conf file is readable:
>>
>> -rw-r--r-- 1 root root 215 Mar 4 05:29 /etc/lxc/lxc-test.conf
>
> The blog shows something like that:
>
> "lxc.utsname = test lxc.network.type = veth lxc.network.flags = up
> lxc.network.link = br0 lxc.network.hwaddr = 4a:49:43:49:79:bd
> lxc.network.ipv4 = 192.168.250.150 lxc.network.ipv6 =
> 2003:db8:1:0:214:1234:fe0b:3596"
>
> The configuration file should be in this format:
>
> lxc.utsname = test
> lxc.network.type = veth
> lxc.network.flags = up
> lxc.network.link = br0
> lxc.network.hwaddr = 4a:49:43:49:79:bd
> lxc.network.ipv4 = 192.168.250.150
> lxc.network.ipv6 = 2003:db8:1:0:214:1234:fe0b:3596
I should have seen that! (I did notice the same problem in one of the
commands. I changed the IP addresses appropriately for my setup but the
comment: "The next commands then reset the IP address of eth0 to
0.0.0.0, but since it is bound to the bridge interface, it will respond
to the previous IP address anyways." does not seem to be true for me and
my normal networking was messed up. Anyway, is it possible to set up
the container without messing with the existing eth0 setup?
Thanks,
Phil.
--
Philip Rhoades
GPO Box 3411
Sydney NSW 2001
Australia
E-mail: phil-8eKeQ+h1VH4pAS55Wn97og@public.gmane.org
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2011-03-07 9:23 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2011-03-03 18:55 Getting started - Error message Philip Rhoades
[not found] ` <4D6FE422.1040807-8eKeQ+h1VH4pAS55Wn97og@public.gmane.org>
2011-03-04 8:08 ` Daniel Lezcano
[not found] ` <4D709E19.2090704-GANU6spQydw@public.gmane.org>
2011-03-07 9:23 ` Philip Rhoades
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.