Hi,
i updated the config file:
lxc.cgroup.memory.limit_in_bytes = 2048M
but my container free -h output shows 32GB
Is there anything that i missed?
--
FIRAT KÜÇÜK
___
lxc-users mailing list
lxc-users@lists.linuxcontainers.org
http://lists.linuxcont
On 29/04/15 17:17, Fırat KÜÇÜK wrote:
lxc.cgroup.memory.limit_in_bytes = 2048M
but my container free -h output shows 32GB
Is there anything that i missed?
For me on ubuntu I had to add this to my default grub line and reboot...
~ grep cgroup /etc/default/grub
GRUB_CMDLINE_LINUX_DEFAULT="quiet
Quoting Alvaro Miranda Aguilera (kiki...@gmail.com):
> Hello,
>
> Can anyone point me in a guide I can use and end with OpenStack using LXD?
>
> I did look over the web, and wasn't able to find anything like a guide
> or howto, so I am asking here in case someone has done and can give an
> idea w
Quoting Fırat KÜÇÜK (firatku...@gmail.com):
> i find the command from this document:
>
> https://github.com/lxc/lxd/blob/master/specs/command-line-user-experience.md
>
> Document can be updated.
Patches welcome and appreciated.
> 0 ✓ serge@sl ~/go/bin $ lxc config set b2 limits.memory 4G
> 0 ✓
Unfortunately it doesn't work.
2015-04-29 10:19 GMT+03:00 Mark Constable :
> On 29/04/15 17:17, Fırat KÜÇÜK wrote:
>
>> lxc.cgroup.memory.limit_in_bytes = 2048M
>> but my container free -h output shows 32GB
>> Is there anything that i missed?
>>
>
> For me on ubuntu I had to add this to my defaul
On Wed, Apr 29, 2015 at 2:17 PM, Fırat KÜÇÜK wrote:
> Hi,
>
> i updated the config file:
> lxc.cgroup.memory.limit_in_bytes = 2048M
>
> but my container free -h output shows 32GB
>
> Is there anything that i missed?
Not really.
In most (all?) lxc setup, various tools (e.g. free, top) on the
cont
in fact.
Today i setup lxd and lxc seperately.
on lxd setup i used:
lxc config set my-container limits.memory 4G
and it worked.
But i considered lxd is not quite stable for production. Than i used lxc
then i created a container and edit conf-file
lxc.cgroup.memory.limit_in_bytes = 2048M
but
I noticed that i have no /sys/fs/cgroup/lxc/ directory. Is it a problem?
Instead: cgmanager and systemd directories exist.
2015-04-29 12:09 GMT+03:00 Fırat KÜÇÜK :
> in fact.
>
> Today i setup lxd and lxc seperately.
>
> on lxd setup i used:
>
> lxc config set my-container limits.memory 4G
>
>
Ah, OK.
In that case, on the container, try:
mount | grep lxcfs
cat /proc/cpuinfo
cat /proc/meminfo
IF you have lxcfs correctly installed and used by the containers (as
shown by mount command), cpuinfo and meminfo should contain
container-specific values as set on cgroups (e.g.
lxc.cgroup.cpuset.
I searched all the packages. I think there is nothing such lxcfs in ubuntu
14.04. LTS trusty.
2015-04-29 12:23 GMT+03:00 Fajar A. Nugraha :
> Ah, OK.
>
> In that case, on the container, try:
> mount | grep lxcfs
> cat /proc/cpuinfo
> cat /proc/meminfo
>
> IF you have lxcfs correctly installed a
https://launchpad.net/~ubuntu-lxc/+archive/ubuntu/lxc-stable
On Wed, Apr 29, 2015 at 4:30 PM, Fırat KÜÇÜK wrote:
> I searched all the packages. I think there is nothing such lxcfs in ubuntu
> 14.04. LTS trusty.
>
>
>
> 2015-04-29 12:23 GMT+03:00 Fajar A. Nugraha :
>>
>> Ah, OK.
>>
>> In that case
I reinstalled the lxc, lxcfs service cannot start.
limit is the same.
Fajar and Guido. Thanks for your support.
BTW I will reinstall the LXD. It is quite user friendly and stable for me.
2015-04-29 12:35 GMT+03:00 Fajar A. Nugraha :
> https://launchpad.net/~ubuntu-lxc/+archive/ubuntu/lxc-
On Wed, Apr 29, 2015 at 5:13 PM, Fırat KÜÇÜK wrote:
> I reinstalled the lxc, lxcfs service cannot start.
... because ?
There should be a log on /var/log/upstart/lxcfs.log.
Or you could try starting it manually:
/usr/bin/lxcfs -s -f -o allow_other /var/lib/lxcfs
--
Fajar
__
call to move_pid_abs (all:/) failed: invalid request
WARNING: failed to escape to root cgroup
call to list_controllers failed: Method "ListControllers" with signature ""
on interface "org.linuxcontainers.cgmanager0_0" doesn't exist
2015-04-29 13:25 GMT+03:00 Fajar A. Nugraha :
> On Wed, Apr 29
How did you install lxcfs?
Looks like your version of cgmanger is not new enough. The ppa should
also have updated cgmanager
... or if you have updated, you might simply need to reboot first.
On Wed, Apr 29, 2015 at 5:29 PM, Fırat KÜÇÜK wrote:
> call to move_pid_abs (all:/) failed: invalid requ
Hi Tycho
>> 2. LXD will work with btrfs subvolumes per environment?
> Eventually, although it currently does not. You can set it up by hand
> if you like, though.
Well, if I want to use the lxc-clone / lxc-snapshot functionality on btrfs
snapshots I guess I have to lxc launch an image first, m
I purged every single dependent package then i installed lxd from
*ppa:ubuntu-lxc/lxd-stable*
Now lxcfs works.
and the result:
root@my-container:/# free -h
total used free sharedbuffers cached
Mem: 2.0G10M 2.0G 492K 0B
Dear Yonsys,
this is a known bug/feature of the controller, You can't
* lower memory.memsw limit_in_bytes below memory.limit_in_bytes
* raise memory.limit_in_bytes above memory.memsw limit_in_bytes
Notice that the default is "infinite" (max integer). For the typical usecase to
lower the li
On Wed, Apr 29, 2015 at 7:10 AM, Jäkel, Guido wrote:
Dear Yonsys,
this is a known bug/feature of the controller, You can't
* lower memory.memsw limit_in_bytes below memory.limit_in_bytes
* raise memory.limit_in_bytes above memory.memsw limit_in_bytes
Notice that the default is "infinite"
Quoting Yonsy Solis (yonsy@gmail.com):
>
>
> On Wed, Apr 29, 2015 at 7:10 AM, Jäkel, Guido wrote:
> >Dear Yonsys,
> >
> >this is a known bug/feature of the controller, You can't
> >
> >* lower memory.memsw limit_in_bytes below memory.limit_in_bytes
> >* raise memory.limit_in_bytes above m
Quoting david.an...@bli.uzh.ch (david.an...@bli.uzh.ch):
> Hi Tycho
>
> >> 2. LXD will work with btrfs subvolumes per environment?
>
> > Eventually, although it currently does not. You can set it up by hand
> > if you like, though.
Stéphane actually pushed a patch yesterday to start supporting
Further..
Now I only have one container running on my system. I redid the steps
1. ran fusermount -uz /var/lib/lxcfs (as service lxcfs start was failing)
2. Start lxcfs..checked the status and it is running
3. Start a container
4. Check lxcfs status and it is in start/running
Now I attach to the
On Wed, Apr 29, 2015 at 8:15 AM, Serge Hallyn
wrote:
lxc-start -n db09
lxc-cgroup -n db09 memory.limit_in_bytes 512M
lxc-cgroup -n db09 memory.memsw.limit_in_bytes 2G
the host have 8GB RAM and 4GB swap.
with htop (and top too) i can see my ram memory in the container
limited to 512M
Hi,
I have created a container say base and I am trying to create a clone of
the base container with backing store as overlayfs. But it always fails
with the following error,
lxc_container: bdev.c: overlayfs_mount: 2237 No such device -
overlayfs: error mounting /var/lib/lxc/base/rootfs onto
/usr
Quoting Rajasekar Darapuram (r...@robinsystems.com):
> here's the log from /var/log/upstart/lxcfs.log
>
> fuse: read too many bytes
> fuse: writing device: Invalid argument
This sounds like a fuse error.
In https://lists.linuxcontainers.org/pipermail/lxc-users/2015-April/009003.html
you said tha
Quoting Yonsy Solis (yonsy@gmail.com):
>
>
> On Wed, Apr 29, 2015 at 8:15 AM, Serge Hallyn
> wrote:
>
> >> lxc-start -n db09
> >> lxc-cgroup -n db09 memory.limit_in_bytes 512M
> >> lxc-cgroup -n db09 memory.memsw.limit_in_bytes 2G
> >>
> >> the host have 8GB RAM and 4GB swap.
> >>
> >> with
I'm getting the same error even for PPA based install
I just rebuilt an ISO with no older versions of LX, installed latest from
PPA
and tried creating a container..
i get the same error.
Thanks
Raj
On Wed, Apr 29, 2015 at 5:48 PM, Rajasekar Darapuram
wrote:
> Recently this issue has been h
BTW we are using kernel 3.13 kernel..can that be any issue?
On Wed, Apr 29, 2015 at 6:56 PM, Rajasekar Darapuram
wrote:
> I'm getting the same error even for PPA based install
> I just rebuilt an ISO with no older versions of LX, installed latest from
> PPA
> and tried creating a container.
28 matches
Mail list logo