t...@cybersource.com.au (Trent W. Buck)
writes:
> I'm being a bit more patient than last time, and I think they ARE
> proceeding, just REALLY slowly. Meanwhile aptitude consumes a 100% of a
> core busy-waiting for a response from dpkg :-/
>
> They look like this:
>
> $ ssh omega cat /proc/771
Daniel Lezcano writes:
> On 01/12/2011 07:39 AM, Trent W. Buck wrote:
>> Mike writes:
>>
Trent W. Buck wrote:
> I can provision a new LXC container, which includes running a few
> "aptitude install foo" lines (inside the containers), and it Just Works.
> If I try to provision tw
"Brian K. White" writes:
> I just use 02:00: which ends up being automatically unique
> enough to not collide with anything else on your subnet assuming you
> already know the ip's you want to use
>
> IP=192.168.0.50 # container nic IP
> HA=`printf "02:00:%x:%x:%x:%x" ${IP//./ }` # generate a M
Gary Ballantyne
writes:
> # /usr/bin/lxc-execute -n foo -f
> /usr/share/doc/lxc/examples/lxc-veth.conf /bin/bash
>
> The container fired up, and I could ping to/from the host. However, when
> I left the container (with "exit") things got weird. In a second
> terminal (already connected to the hos
Daniel Lezcano writes:
> On 02/02/2011 10:26 AM, Trent W. Buck wrote:
>> For each lxc.network.type = veth, if you DON'T specify an
>> lxc.network.hwaddr, you get one assigned at random (example below).
>>
>> Are these assignments made from a reserved range (a la 169.254/16 in
>> IPv4), or are the
On 2/2/2011 1:13 PM, Trent W. Buck wrote:
> Gary Ballantyne
> writes:
>
>> Would greatly appreciate any help getting the sshd template working on
>> my Ubuntu 9.10 host.
>
> I recommend you upgrade to 10.04 LTS and try again. 9.10 will be
> end-of-lifed by Canonical in three months, after whic
Yeah, it's quite easy to do this. Here's my lxc network config from one of
my machines:
lxc.network.type = veth
lxc.network.flags = up
lxc.network.link = br1
lxc.network.ipv4 = 192.168.0.4/24
My outside network is eth0/br0, and my inside network is just br1. I add
these rules to forward br0 to
Hello
My host is configured with two networks as below:
eth0: external network a.b.c.d/24
eth1: internal network 10.1.0.0/16
I would like to configure my containers to belong to a third network
(say, 10.2.0.0/16), and then set up two NAT rules (one for eth0 and one
for eth1) to allow them to acc
On 2/2/2011 6:20 AM, Daniel Lezcano wrote:
> On 02/02/2011 10:26 AM, Trent W. Buck wrote:
>> For each lxc.network.type = veth, if you DON'T specify an
>> lxc.network.hwaddr, you get one assigned at random (example below).
>>
>> Are these assignments made from a reserved range (a la 169.254/16 in
>>
On 02/02/2011 10:26 AM, Trent W. Buck wrote:
> For each lxc.network.type = veth, if you DON'T specify an
> lxc.network.hwaddr, you get one assigned at random (example below).
>
> Are these assignments made from a reserved range (a la 169.254/16 in
> IPv4), or are they randomized across the entire a
On 02/02/2011 01:15 AM, Trent W. Buck wrote:
> Daniel Lezcano writes:
>
>> On 02/01/2011 12:04 PM, Dean Mao wrote:
>>> Hi,
>>>
>>> I've been messing around with trying to get the output of lxc-start into a
>>> file some. I know that lxc-start produces a log file, as well as the
>>> ability to fet
t...@cybersource.com.au (Trent W. Buck)
writes:
> Further, when manually allocating a static hwaddr (so I can map it to an
> IP within the DHCP server), is there any particular range I should avoid
> or stick to?
On further reading, I see there are apparently reserved address regions
for private
For each lxc.network.type = veth, if you DON'T specify an
lxc.network.hwaddr, you get one assigned at random (example below).
Are these assignments made from a reserved range (a la 169.254/16 in
IPv4), or are they randomized across the entire address space? AFAICT,
it MUST be the latter.
Further
13 matches
Mail list logo
