Hello,
I've encountered this bug with lxc-0.9.0, using the lxc-phys scenario -
assigning a physical interface to a container.
In my understanding, this is what happens when a container starts (well, the
relevant parts):
- the configuration file is parsed into a config structure - the kernel
Branch: refs/heads/master
Home: https://github.com/lxc/lxc
Commit: ff4bacf71a3078cb2b926bfb248266236da9b1eb
https://github.com/lxc/lxc/commit/ff4bacf71a3078cb2b926bfb248266236da9b1eb
Author: S.Çağlar Onur cag...@10ur.org
Date: 2013-11-13 (Wed, 13 Nov 2013)
Changed paths:
Branch: refs/heads/master
Home: https://github.com/lxc/lxc
--
DreamFactory - Open Source REST JSON Services for HTML5 Native Apps
OAuth, Users, Roles, SQL, NoSQL, BLOB Storage and External API Access
Free app
On Wed, Nov 13, 2013 at 12:39:00AM -0500, S.Çağlar Onur wrote:
Adding block/char devices to running container is a common operation so
provide a common implementation for users to consume.
changes since v2;
* lets the user set an alternate path inside the container as Stéphane
suggested
Branch: refs/heads/master
Home: https://github.com/lxc/lxc
Commit: a9a0ed90dd1cdadd412576a45af16419efc0e939
https://github.com/lxc/lxc/commit/a9a0ed90dd1cdadd412576a45af16419efc0e939
Author: S.Çağlar Onur cag...@10ur.org
Date: 2013-11-13 (Wed, 13 Nov 2013)
Changed paths:
Quoting Stéphane Graber (stgra...@ubuntu.com):
Hello,
We recently got reports of the recent changes to lxc-info breaking
existing scripts.
In my own case, I have a host with several containers where a backup
script uses 'lxc-info -n $container -p | awk ...' to get the init pid,
then rsyncs
Signed-off-by: S.Çağlar Onur cag...@10ur.org
---
src/lxc/lxclock.c | 74 +--
src/lxc/lxclock.h | 3 +++
src/lxc/utils.c | 57 +-
3 files changed, 65 insertions(+), 69 deletions(-)
diff --git
