On 2013/11/8 23:53, Stéphane Graber wrote:
On Fri, Nov 08, 2013 at 05:22:28PM +0800, Qiang Huang wrote:
Hi, list:
Hope website administrator can see this.
http://linuxcontainers.org/
In the beginning part,
===
Current LXC uses the following kernel features to contain processes:
Kernel
Last year I've read many times, that LXC have some outstanding security
issues, and are the encapsulation is not tight enough to prevent
hijacking the host, when the guest is compromised. But I never managed
to find out, how exactly does one escape the LXC container.
I'm using the LXC
On 11.11.2013 13:43, Daniel P. Berrange wrote:
On Mon, Nov 11, 2013 at 01:19:25PM +0100, Adam Ryczkowski wrote:
Last year I've read many times, that LXC have some outstanding
security issues, and are the encapsulation is not tight enough to
prevent hijacking the host, when the guest is
On Mon, Nov 11, 2013 at 01:49:11PM +0100, Adam Ryczkowski wrote:
On 11.11.2013 13:43, Daniel P. Berrange wrote:
On Mon, Nov 11, 2013 at 01:19:25PM +0100, Adam Ryczkowski wrote:
Last year I've read many times, that LXC have some outstanding
security issues, and are the encapsulation is not
On 11/11/2013 06:04 PM, Leonid Isaev wrote:
On your system run
$ lxc-checkconfig | grep User namespace
to check if user namespaces are enabled on your host.
That's correct:
$ lxc-checkconfig | grep User namespace
User namespace: enabled
$ lsb_release -a
No LSB modules are available.
In general,
I've found that LXC networking is no different than any other type of
virtualizaion.
In fact,
If you implement libvirt, the virtual networking objects (ie br,
virbr, etc) once created can be utilized by any/all virtual networking
technologies.
So, for example I also have KVM
Quoting Adam Ryczkowski (adam.ryczkow...@statystyka.net):
On 11.11.2013 13:43, Daniel P. Berrange wrote:
On Mon, Nov 11, 2013 at 01:19:25PM +0100, Adam Ryczkowski wrote:
Last year I've read many times, that LXC have some outstanding
security issues, and are the encapsulation is not tight
On 11/11/2013 10:23 PM, Serge Hallyn wrote:
You can get the support either from ppa:ubuntu-lxc/kernel, or by
installing the trusty kernel. The trusty kernel has had some issues
until last week (including upstream bugs), but I think it should be
usable now.
I probably will wait until the
Quoting brian mullan (bmullan.m...@gmail.com):
As soon as I do, I will in a few days try to document what I've done so
others interested in the same don't have to go through
the same research.
Thanks, I look forward to seeing it. The current
Quoting Tamas Papp (tom...@martos.bme.hu):
On 11/11/2013 10:23 PM, Serge Hallyn wrote:
You can get the support either from ppa:ubuntu-lxc/kernel, or by
installing the trusty kernel. The trusty kernel has had some issues
until last week (including upstream bugs), but I think it should be
I'm not sure the lxc-user alias will take an file attachment or not. If
not I'll try something else.
I tried to document everything I did to finally get sound working in an LXC
container on my Ubuntu 13.10 system.
I've attached that as a .ODT (librewriter) file to this email because I
tried to
Thank you for the reply. I may be not clear in the original question.
For example, in KVM, the system setup a virtual network device pair in
host, and added on end to bridge. So when an program is using the other
end, its communication will be bridged to actual hardware. And KVM exposes
a virtual
On Tue, Nov 12, 2013 at 1:22 PM, Magicloud Magiclouds
magicloud.magiclo...@gmail.com wrote:
Thank you for the reply. I may be not clear in the original question.
For example, in KVM, the system setup a virtual network device pair in
host, and added on end to bridge. So when an program is
13 matches
Mail list logo
