Hi all,
I have noticed that changing the overcommit
(/proc/sys/vm/overcommit_memory) mode inside a container change the
overcommit mode of the host. Is it normal ?
For /proc/sys/kernel/shmmax, the value seems to be local to the container.
Regards,
Bertrand
PS : my LXC version : 1.0.1
Ok. Thx you for information.
It's very very dangerous :(
Bertrand
On Thu, Oct 9, 2014 at 10:15 AM, Tamas Papp tom...@martos.bme.hu wrote:
On 10/09/2014 10:07 AM, Bertrand Paquet wrote:
Hi all,
I have noticed that changing the overcommit
(/proc/sys/vm/overcommit_memory) mode inside a
Hello.
I'm making a tool using Python.
I made a tool almost.
But, I have a point that I understand.
I want to copy a file in local into the container.
How should I do it.
Please teach me.
Best Regard,
Noriki
___
lxc-users mailing list
Hi,
I am using lxc-create on the latest version of Linux Mint. Following is the
error message
sudo lxc-create -n ubuntu01 -t ubuntu
Checking cache download in /var/cache/lxc/precise/rootfs-amd64 ...
Installing packages in template: ssh,vim,language-pack-en
Downloading ubuntu precise minimal ...
you can use standard scp or read the content of the file and then attach
against the container, then write the file inside attach,
On Thu, Oct 9, 2014 at 4:50 AM, Noriki Nakamura bynn_ch...@tencho-lab.net
wrote:
Hello.
I'm making a tool using Python.
I made a tool almost.
But, I have a
I spun up a Jessie container in my Fedora 20 (x86_64, LXC 1.0.5) box and
the journald process inside the host consumes full CPU time for one core.
I've Googled a bit and found some reports of that being connected to a bug
that is allegedly already fixed in systemd, or related to the kmsg device
Hi all,
I have noticed that changing the overcommit
(/proc/sys/vm/overcommit_memory) mode inside a container change the
overcommit mode of the host. Is it normal ?
For /proc/sys/kernel/shmmax, the value seems to be local to the container.
Regards,
Bertrand
PS : my LXC version : 1.0.1
Try this one:
Export http_proxy=http://proxy:port/;
If debootstrap uses it, then it should work.
Also don't forget to apply apt settings in container.
On October 9, 2014 4:47:34 PM sriram patil spsrirampa...@gmail.com wrote:
Hi,
I am using lxc-create on the latest version of Linux Mint.
On Thu, 2014-10-09 at 08:27 -0300, Daniel Miranda wrote:
I spun up a Jessie container in my Fedora 20 (x86_64, LXC 1.0.5) box
and the journald process inside the host consumes full CPU time for
one core.
I've Googled a bit and found some reports of that being connected to a
bug that is
Hi,
There was no problem with apt but, I had issue using debootstrap. Had to
set up the proxy settings in /etc/wgetrc. All fine now.
Thanks for the help. :)
On Thu, Oct 9, 2014 at 8:54 PM, Michael H. Warfield m...@wittsend.com
wrote:
Hey Tamas!
On Thu, 2014-10-09 at 16:59 +0200, Tamas Papp
Quoting Bertrand Paquet (bertrand.paq...@gmail.com):
Hi all,
I have noticed that changing the overcommit
(/proc/sys/vm/overcommit_memory) mode inside a container change the
overcommit mode of the host. Is it normal ?
Yes, sadly those are not namespaced. The apparmor (and hopefully selinux,
Quoting Bertrand Paquet (bertrand.paq...@gmail.com):
Ok. Thx you for information.
It's very very dangerous :(
You at a very minimum should be using apparmor, selinux, or user namespaces.
Preferably user namespaces and one of apparmor or selinux.
-serge
Hi folks,
I've been working with Ceph and Docker containers, and wanted to post a
reply to Omar Marquez's post to the list from October 2013 regarding issues
using Ceph's `rbd map` command within a Linux container:
https://lists.linuxcontainers.org/pipermail/lxc-users/2013-October/005795.html
I
Any advice of tracking down the cause of various zombies on my LXC
containers?
I used to have zombie problems on my LXC hosts as well, but this was the
LXC API bug that was fixed in 1.0.6 (just installed from trusty-proposed).
However my zombie problems inside my Trusty containers persist. One
14 matches
Mail list logo
