No. However, you should be able to hack it up pretty easily in
userspace by comparing /proc/$$/ns/pid. It requires privilege,
but a very simple, easy-to-verify helper which simply takes one
argument and returns 0 if /proc/$1/ns/pid is the same as
/proc/self/ns/pid should be trustable with
So the info from where the container runs is in the per-container config.
Csordás Csaba Ifj.
On Tue, Feb 19, 2013 at 11:53 PM, Serge Hallyn serge.hal...@ubuntu.com wrote:
Quoting Papp Tamas (tom...@martos.bme.hu):
On 02/11/2013 04:11 AM, Serge Hallyn wrote:
Agreed, please do get us
John l...@jelmail.com a écrit :
lxc.cgroup.devices.allow = c 195:* rwm # for nvidia
This is what I have too. I am on Arch Linux.
I can start and log into my container. Then I created /dev/nvidia0,
/dev/nvidia1 and /dev/nvidiactl in the container.
I have
/dev/nvidia0 c 195 0 mode 666
Hi,
there is a suggestion at http://lxc.sourceforge.net/man/lxc.html:
make accessible from the container the resolv.conf file belonging to the host.
/etc/resolv.conf /home/root/debian/rootfs/etc/resolv.conf none bind 0 0
When using this with live-deboconfig, i.e.:
lxc-debconfig
Quoting Csordás Csaba Ifj. (cscsor...@gmail.com):
Hi,
there is a suggestion at http://lxc.sourceforge.net/man/lxc.html:
make accessible from the container the resolv.conf file belonging to the host.
/etc/resolv.conf /home/root/debian/rootfs/etc/resolv.conf none bind 0 0
When using
On 02/20/2013 10:21 PM, Csordás Csaba Ifj. wrote:
When using this with live-deboconfig, i.e.:
s/live-debconfig/lxc-debconfig/
in both cases, the bug reports should go to the debian bts (against
live-debconfig, or, in this case, against lxc).
however, i've fixed that in git, thanks.
--
somone fix this finally..
On 02/21/2013 06:29 AM, mailer-dae...@mail.mailbrush.com wrote:
Failed to deliver to 'msklizman...@ebuddy.com'
SMTP module(domain mail-in.ebuddy.com:25) reports:
host mail-in.ebuddy.com:25 says:
550 5.1.1 User unknown
Reporting-MTA: dns; mail.mailbrush.com
