Hi,
I'm working on constructing a Debian template in a linux container.
As I normally do not work on a Debian system, I'm working on a Virtualbox
with Debian Wheezy (testing) and lxc 0.8.0~rc1-4 installed.
I used a preseed configuration file (http://pastebin.com/SR5YXBqE). (Notice
the puppet
On Mon, Jul 9, 2012 at 10:37 AM, Fajar A. Nugraha l...@fajar.net wrote:
On Mon, Jul 9, 2012 at 3:16 PM, Glenn Daneels glenndane...@gmail.com
wrote:
Hi,
I'm working on constructing a Debian template in a linux container.
As I normally do not work on a Debian system, I'm working on a
I found out what was missing in my debian template script. My config file
asked for 6 tty's while probably only 2 got constructed (seems to be
default by Squeeze), so I added:
# squeeze only has /dev/tty and /dev/tty0 by default,
# therefore creating missing device nodes for tty1-4.
Hello!
I habe a new container set up (precise on precise) and it works well.
Network configuration is:
lxc.network.type=veth
lxc.network.link=br0
lxc.network.flags=up
lxc.network.hwaddr = [...]:ed:d8
lxc.network.ipv4 = 84.16.228.72/32
if i add a second id address:
lxc.network.type=veth
On 07/09/2012 10:43 AM, Matthias P. Würfl wrote:
Hello!
I habe a new container set up (precise on precise) and it works well.
Network configuration is:
lxc.network.type=veth
lxc.network.link=br0
lxc.network.flags=up
lxc.network.hwaddr = [...]:ed:d8
lxc.network.ipv4 = 84.16.228.72/32
Am 09.07.2012 17:29, schrieb Stéphane Graber:
This isn't LXC specific, what's happening in your case is that you're
contacting eth1 but getting a reply from eth0 as that's where your
default route is.
OK, but in real world (without LXC) I'd configure eth0 and eth0:1.
This doesn't work with
