> I'm using your template on an Ubuntu 12.04 stock LXC install. I've run into
> a problem trying to use shared memory with Python's multiprocessing library.
> It relies on /dev/shm using tmpfs. I tried mounting it with an entry:
>
> lxc.mount.entry = tmpfs /dev/shm tmpfs defaults 0 0
>
> and
> I would like it know is it possible to create a single rootfs (might
> be in read-only mode) and share it among multiple containers ?
At Dotcloud.com they use one basic OS rootfs. For each container they
mount this OS rootfs read-only and use a union file-system (AUFS) to add
a writable layer.
On Fri, 2013-05-24 at 11:26 +0100, Rory Campbell-Lange wrote:
> I'd be grateful for assistance trying to get a minimal Debian 7 lxc system
> running on a Debian 7 host.
>
The debian template that comes with Wheezy is broken. Solution: use
another template. See:
http://sourceforge.net/mailarchiv
> I'm trying to get LXC to work for me on Debian Wheezy/amd64 and I'm having a
> Hellish time. I'm following the advice on wiki.debian.org and other places,
> and I believe I'm creating my containers correctly, but when I launch a
> container, I get a bunch of messages about needing root to set a h
> My intention is to have a container running nginx as a reverse proxy
> and containers running the various combinations of Apache, PHP, RoR,
> MySQL, etc software for the web apps I want. After experimenting
> (mixed success) with combinations of the Ubuntu default lxcbr0 (nginx
> container attac
> What is the best way to broadcast container's hostname to host?
> I want to be able to ssh from host into the container using its
> hostname as handle, instead of an IP address.
>
> I'm using the default template in Ubuntu 12.04.
> I have made a container template that I want to reuse.
My s
On Wed, 2012-12-12 at 08:52 -0600, Serge Hallyn wrote:
> Quoting Rob van der Hoeven (robvanderhoe...@ziggo.nl):
> > I would really like an extra lxc.mount.cwd entry in the configuration
> > file. Maybe this entry should be mandatory if the containers filesystem
> > is di
> > So the lxc.mount.entry statement works but lxc-execute does not change
> > its working directory to a valid entry inside the containers filesystem.
> > It's a small problem, maybe i'm doing something wrong?
>
> Not really. It is doing what you think it's doing. But I'm not sure
> how it shou
Hi,
I want to use lxc-execute to isolate programs from the users data. For
this I created the following lxc configuration file:
Name: /home/rob/lxctest/lxc02.conf
Contents:
lxc.utsname=lxc02
lxc.mount.entry=/home/rob/lxctest/home /home none bind,defaults 0 0
The lxctest/home directory is empt