[Lxc-users] Can't execute a python shell script from /run/*

We're running an app that installs some files to /run and needs to execute a python script in that directory. Even the root user is denied permission to execute the script, which tells me that LXC (presumably AppArmor) is blocking access to running a script under /run/* I uncommented lxc.aa

[Lxc-users] Can't execute a python shell script from /run/*

We're running an app that installs some files to /run and needs to execute a python script in that directory. Even the root user is denied permission to execute the script, which tells me that LXC (presumably AppArmor) is blocking access to running a script under /run/* I uncommented lxc.aa_pr

Re: [Lxc-users] Can't execute a python shell script from /run/*

On Mon, Apr 22, 2013 at 2:44 PM, David Parks wrote: > We’re running an app that installs some files to /run and needs to > execute a python script in that directory. > > ** ** > > Even the root user is denied permission to execute the script, which tells > me that LXC (presumably AppArmor) is

Re: [Lxc-users] Can't execute a python shell script from /run/*

On 04/22/2013 10:02 AM, Fajar A. Nugraha wrote: > On Mon, Apr 22, 2013 at 2:44 PM, David Parks > wrote: > > We’re running an app that installs some files to /run and needs to > execute a python script in that directory. > > __ __ > > Even the r

Re: [Lxc-users] Problem with: lxc.autodev=1

Le samedi 20 avril 2013 à 15:33 -0400, Michael H. Warfield a écrit : > On Sat, 2013-04-20 at 21:13 +0200, Andreas Otto wrote: > > Hi all, > > > my problem: the "autodev" create devices with wrong permissions: > > > > ls -ald /dev/* > > crw-rw 1 root tty 136, 16 Apr 20 18:34 /dev/console > >

Re: [Lxc-users] Problem with: lxc.autodev=1

Le samedi 20 avril 2013 à 21:13 +0200, Andreas Otto a écrit : > Hi all, > > my problem: the "autodev" create devices with wrong permissions: > > > ls -ald /dev/* > crw-rw 1 root tty 136, 16 Apr 20 18:34 /dev/console > lrwxrwxrwx 1 root root 11 Apr 20 18:34 /dev/core -> /proc/kcore > lr

Re: [Lxc-users] Problem with: lxc.autodev=1

Am 22.04.2013 10:28, schrieb Frederic Crozat: > Le samedi 20 avril 2013 à 21:13 +0200, Andreas Otto a écrit : >> Hi all, >> >> my problem: the "autodev" create devices with wrong permissions: >> >> > ls -ald /dev/* >> crw-rw 1 root tty 136, 16 Apr 20 18:34 /dev/console >> lrwxrwxrwx 1 root r

Re: [Lxc-users] Can't execute a python shell script from /run/*

Ah, You are a scholar and a gentleman Fajar. Your email just saved us untold hours of toil. Now I see how those FS's are mounted, I wasn't aware of this other fstab, I removed the noexec mount option and all is well now. We've been tracking a related issues for 4 days now. Thank you!! Incidenta

Re: [Lxc-users] Can't execute a python shell script from /run/*

On Mon, Apr 22, 2013 at 3:18 PM, Stéphane Graber wrote: > On 04/22/2013 10:02 AM, Fajar A. Nugraha wrote: > > Now what's interesting is that my ubuntu template (0.9.0-0ubuntu2) > > specifically create an empty /lib/init/fstab > > The Ubuntu template only clears /lib/init/fstab if you're using th

Re: [Lxc-users] Problem with: lxc.autodev=1

Hi, as one solution I try to switch my lxc container on opensuse 12.3 back to sysvinit-init but this seems not to work eigther... # zypper --root /var/lib/lxc/nhi2/rootfs in sysvinit-init Daten des Repositories laden ... Installierte Pakete lesen ... Paketabhängigkeiten auflösen ... Problem:

Re: [Lxc-users] Problem with: lxc.autodev=1

Le lundi 22 avril 2013 à 10:43 +0200, Andreas Otto a écrit : > Am 22.04.2013 10:28, schrieb Frederic Crozat: > > Le samedi 20 avril 2013 à 21:13 +0200, Andreas Otto a écrit : > >> Hi all, > >> > >> my problem: the "autodev" create devices with wrong permissions: > >> > >> > ls -ald /dev/* > >> cr

[Lxc-users] Problem with core dumps generated from containers, apport

system: x86_64, ubuntu 12.10 with a ubuntu template container When I enable core dumps in a container and such get generated, apport on the host gets confused and creates bogus (it seems) crash reports. If I speculate it could be that apport gets a non translated container pid from the kernel,

Re: [Lxc-users] Problem with: lxc.autodev=1

> Ok. I'll do more tests on my side. But you should open a bug report on > https://bugzilla.novell.com/ against openSUSE (and assign it to me) so > we don't loose it. -> done -- Precog is a next-generation analytics pla

[Lxc-users] Strange prob w/Ubuntu 13.04 and LXCBR0 disappearing after reboots

I know Ubuntu 13.04 is still beta but I've been seeing a wierd problem on my system where sometimes after a reboot or booting after the computers been off for awhile... I have noticed that LXCBR0 bridge has disappeared after a reboot. Today it happened again. To restore I just do sudo apt-get r

Re: [Lxc-users] Packet forwarding performance drop with 1000 containers

Quoting Benoit Lourdelet (blour...@juniper.net): > Hello, > > I am testing forwarding performance of 1000 containers running at the same > time. > I am running Linux 3.8.5 and lxc 0.8.0. > > Each container is a simple router : 2 IPv4 interfaces, The routing table is > very small : 3/4 routes

Re: [Lxc-users] LXC start doesn't work

Quoting Mukanyiligira Didacienne (siyana...@gmail.com): > Hello I have tried to create containres and this is the message I am > getting when I type in the terminal the following command: > > $ sudo lxc-start -n left /bin/bash > > lxc-start: Device or resource busy - failed to remove previous cgr

Re: [Lxc-users] Problem with core dumps generated from containers, apport

My guess would be similar to this but slightly different. I'd guess that apport on the host sees the SEGV in kernel log. That will have the correct pid for the kernel to look up the task, however it will crosscheck /proc/$$/maps and such against userspace on the host, which will cause debug info

[Lxc-users] How long the dhcp lease lasts

Hello everyone, Using the default config, containers will have their IP attributed by the dnsmasq service. I'd like to write in the '/etc/hosts' file of the host system the hostname and the corresponding IP address of each container I start. I will then use this hostname in an iptable rules for

Re: [Lxc-users] How long the dhcp lease lasts

On Mon, 2013-04-22 at 21:59 +0200, Robin Monjo wrote: > Hello everyone, > > Using the default config, containers will have their IP attributed by > the dnsmasq service. I'd like to write in the '/etc/hosts' file of the > host system the hostname and the corresponding IP address of each > container

Re: [Lxc-users] How long the dhcp lease lasts

Thank you for your answer. I want to have the hostname and ip written in the /etc/hosts file so I can access them directly using their hostname and not their ip. For example, I'd like to ping the hostname rather than the ip. I will document myself on dnsmasq to get a better understanding of ever

Re: [Lxc-users] Need simple configuration for embedded ARM LXC

Quoting Serge Hallyn (serge.hal...@ubuntu.com): > Quoting Daniel Lezcano (daniel.lezc...@free.fr): > > On 04/20/2013 03:23 AM, Somnath Mitra wrote: > > > Is there a workaround/resolution to this? > > > > > > I had filed a > > > bug > > > http://sourceforge.net/tracker/?func=detail&aid=3610837&grou

Re: [Lxc-users] How long the dhcp lease lasts

On Mon, 2013-04-22 at 22:58 +0200, Robin Monjo wrote: > Thank you for your answer. > I want to have the hostname and ip written in the /etc/hosts file so I > can access them directly using their hostname and not their ip. For > example, I'd like to ping the hostname rather than the ip. But... You

Re: [Lxc-users] How long the dhcp lease lasts

I find it best to separate, entirely, the base host cluster management network from the container cluster network, entirely. On Mon, Apr 22, 2013 at 2:46 PM, Michael H. Warfield wrote: > On Mon, 2013-04-22 at 22:58 +0200, Robin Monjo wrote: > > Thank you for your answer. > > I want to have the h