Thanks. That worked.
I used [path-to-container]/run/shm because I got Permission Denied
when using /dev/shm, which after booting is symlinked to /run/shm.
-Randall
On 09/17/2013 01:33 AM, Andreas Laut wrote:
Hi.
For lxc.mount.entry you have to write down the path from sight of your
host.
Sorry I don't have the older emails in this thread, but the
preferred syntax is to use a path relative to your container
rootfs, i.e. 'run/shm', i.e.
lxc.mount.entry = tmpfs run/shm tmpfs defaults 0 0
If that is not working then there's a bug.
-serge
Quoting Randall Smith (rand...@tnr.cc):
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
Rob,
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
On 05/11/2013 04:41 AM, Mason Loring Bliss wrote:
Hi there!
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
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
