Hi Folks,
I am trying to run fork bomb test inside a container to measure the
extent of isolation containers provide. I am observing that even after
putting all the available limits my host system becomes unresponsive
after some time. Can someone throw light what should be the issue?
Doesn't
Hi,
I'm running lxc-1.0.6-r1 on Gentoo. I can create my lxc container and ssh
into it and everything looks fine.
lxc-create -n u1 -t download -- --no-validate --dist ubuntu --release
trusty --arch amd64
lxc-start -n u1
However, lxc-attach runs programs in the host's root, not in the container
Hi,
I'm getting:
resize2fs 1.42 (29-Nov-2011)
resize2fs: Device or resource busy while trying to open /dev/mapper/vg0-lxc01
Couldn't find valid filesystem superblock
The device is not mounted elsewhere, its only in use has the LXC
rootfs, so why would the online resize not work?
Thanks
__
Hello,
I dont know much about container configuration, but 169.x.x.x is assigned
by DHCP when it cannot assign any other valid IP.
May be you want check on those lines.
Cheers!
Durga
On Thu, Nov 20, 2014 at 12:46 AM, Denis Müller wrote:
> Hi,
>
> i created two containers:
>
> centos1 (ip 10.
Hi,
i created two containers:
centos1 (ip 10.0.3.2)
centos2 (ip 10.0.3.3)
on this machine, i have created a bridge "lxcbr0" (Adress:10.0.3.1
Bcast:10.0.3.255 Mask:255.255.255.0) with dnsmasq deamon attached on this
interface.
/etc/dnsmasq.conf:
listen-address=10.0.3.1
bind-interfaces
d
On 11/19/2014 11:02 AM, Denis Müller wrote:
Hi,
i'm using centos 6 and lxc 1.06, but i can't start my container
/var/lib/lxc/centos1/config:
##
lxc.network.type = veth
lxc.network.flags = up
lxc.network.link = lxcbr0
lxc.network.hwaddr = fe:5f:fa:6a:96:44
lxc.rootfs = /var/lib/lxc/centos1
Hi,
i'm using centos 6 and lxc 1.06, but i can't start my container
/var/lib/lxc/centos1/config:
##
lxc.network.type = veth
lxc.network.flags = up
lxc.network.link = lxcbr0
lxc.network.hwaddr = fe:5f:fa:6a:96:44
lxc.rootfs = /var/lib/lxc/centos1/rootfs
lxc.include = /usr/share/lxc/config/ce
