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 two containers at the same time, both containers
>>> appear to hang with a dpkg process
Doesn't aptitude write into the home directory that you're sharing
across containers? locks ~/.aptitude/cache?
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 provisio
On Tue, Jan 11, 2011 at 5:34 PM, Nirmal Guhan wrote:
> On Tue, Jan 11, 2011 at 5:25 PM, Nirmal Guhan wrote:
>> Hi,
>>
>> How do I forward packets (ethernet frames included) from host to
>> container. I plan to run a packet capture program (tcpdump for
>> instance) within container that will captu
On Tue, Jan 11, 2011 at 5:25 PM, Nirmal Guhan wrote:
> Hi,
>
> How do I forward packets (ethernet frames included) from host to
> container. I plan to run a packet capture program (tcpdump for
> instance) within container that will capture the packets coming to
> host eth1 interface. I tried both
Hi,
How do I forward packets (ethernet frames included) from host to
container. I plan to run a packet capture program (tcpdump for
instance) within container that will capture the packets coming to
host eth1 interface. I tried both using bridge and iptables but they
do not seem to help.
iptables
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 two containers at the same time, both containers
appear to hang with a dpkg process in the D state[0].
Has anybody run into this before?
Mike writes:
> This has sort of been mentioned earlier on this list.
>
> I noticed netfilter messages getting trashed in the various
> /var/log/messages on a system with two containers, netfilter rules on
> the host, and each container and the host running rsyslog. On closer
> inspection, I r
On Tue, Jan 11, 2011 at 4:12 PM, Mike wrote:
> Nirmal Guhan wrote:
>> Did you try macvlan instead of veth?
>
> No, it looked "bleeding edge", and it didn't occur to me how I could use
> it. How would one? What is it?
>
Try
lxc.network.type = macvlan
lxc.network.link = eth0
-Nirmal
Nirmal Guhan wrote:
> Did you try macvlan instead of veth?
No, it looked "bleeding edge", and it didn't occur to me how I could use
it. How would one? What is it?
--
Protect Your Site and Customers from Malware Attacks
On Fri, Jan 7, 2011 at 5:39 PM, Mike wrote:
> The instructions that I've seen for LXC suggest creating a bridge in the
> host, placing its name in lxc.network.link.
>
> On a diskless system I have eth0 & eth1, and create the bridge on eth1.
> I can't put eth0 in a bridge, because it's the port for
On Sun, 9 Jan 2011 13:25:53 +0100, Patrick Winnertz
wrote:
> Hello,
>
> I've tried the last days hard to set up working lxc containers on a
grsec
> enabled kernel. However I failed everytime with several error msgs
and/or
> kernel oopses.
>
> After booting in the grsec kernel I've verified wi
11 matches
Mail list logo
