Hi ,
Just brought up 4 centos containers on a 4CPU 16G machine . Memory wise the
machine is doing really well but have issue with the CPU hitting 100% .
'top' shows me that system is constantly using 70% and remaining by users.
There are just plain 'getty' terminals that are running for each of th
that sounds very exciting! drop a line in the mailing list if you do
opensource some bits. Im trying out similar stuff but the HA layer is done
by L7 tools (mostly due to limitations imposed by public clouds and
latencies), also the tooling setup (including container management) is done
using chef.
Tangentially related story: I have a highly dynamic topology (many
VLANs created/destroyed frequently). I use the following structure:
Host = 2 x NICs, joined as 1 x bond0 interface with failover
VLANs = bond0 interface linked, negotiated dynamically based upon
requirements of hosted containers, a
sorry, i should have been more clear.
seems you are trying to mount /a into /a that won't work.
at those level, where are the logical volumes mounted?
Say you want to share
/media/lv1
into container as /media/lv1
then, the line should be:
lxc.mount.entry= /media/lv1
/var/lib/lxc/ldap_ban
Hi Serge,
btw - great support! Always very fast responses!!! like it :)
Its Ubuntu 14.04 dev amd64... and it IS working... don't ask me what was
wrong... maybe I tried to fast after a reboot. Looks like glusterfs mounts
take some time.
sorry :(
Regards,
Flo
On Wed, Feb 12, 2014 at 5:12 PM, Se
Quoting David Shwatrz (dshwa...@gmail.com):
> Hi, LXC users,
>
> Is there any difference between
> setting a mount entry via /etc/fstab in the root filesystem of a
> container or as lxc.mount.entry in the LXC config file?
Yes - lxc.mount.entry mounts are done by lxc, before the pivot_root.
So you
> >
> > but not on startup.
>
> This sounds like an issue with your distro's init/mountall. LXC is
> not involved with the container's /etc/fstab. So we'd need more
> information on the container distro+version for anyone to be able
> to help you.
>
It could also be related to a "wrong" boot ord
Hi, LXC users,
Is there any difference between
setting a mount entry via /etc/fstab in the root filesystem of a
container or as lxc.mount.entry in the LXC config file?
Regards,
DavidS
___
lxc-users mailing list
lxc-users@lists.linuxcontainers.org
http:/
Quoting Robin Monjo (robin.mo...@applidget.com):
> Hello,
>
> Thank you for the answers. My problem is when I untar my rootfs. Got lots of
> errors such as:
>
> tar: ./rootfs/dev/mixer: Cannot mknod: Operation not permitted
> tar: ./rootfs/dev/ram5: Cannot mknod: Operation not permitted
> tar: .
Hello,
Thank you for the answers. My problem is when I untar my rootfs. Got lots of
errors such as:
tar: ./rootfs/dev/mixer: Cannot mknod: Operation not permitted
tar: ./rootfs/dev/ram5: Cannot mknod: Operation not permitted
tar: ./rootfs/dev/midi01: Cannot mknod: Operation not permitted
tar: ./
Quoting Flo (florian.engelm...@gmail.com):
> Hi,
>
> I try to mount a glusterfs volume on LXC startup. Adding to /etc/fstab:
>
> 192.168.219.171:/homes /export/home glusterfs defaults,_netdev 0 0
>
> does mount the volume if I run
>
> mount -a
>
> but not on startup.
This sounds like an issue
Hi,
I try to mount a glusterfs volume on LXC startup. Adding to /etc/fstab:
192.168.219.171:/homes /export/home glusterfs defaults,_netdev 0 0
does mount the volume if I run
mount -a
but not on startup.
Adding 192.168.219.171:/homes export/home glusterfs defaults,_netdev 0 0
to /var/lib/lxc/
12 matches
Mail list logo
