On 01/07/2011 03:13 AM, Mike Ivanov wrote:
On 11-01-06 6:02 PM, Mike Ivanov wrote:
# lxc-execute -n xxx -f config /bin/bash
r...@xxx:/# lxc-execute: Input/output error - failed to read
BTW, exactly the same happens to containers created with the lxc-sshd
template.
When you created a system
Yea i know btrfs has snapshot abilities but my entire server is ext4. I
could format a extra drive with btrfs. Would that allow me to use btrfs for
containers? Are there any other ideas or processes i can try out?
On Thu, Jan 6, 2011 at 12:50 PM, C Anthony Risinger anth...@extof.mewrote:
On
On 01/07/2011 03:18 AM, matthew byers wrote:
Yea i know btrfs has snapshot abilities but my entire server is ext4. I
could format a extra drive with btrfs. Would that allow me to use btrfs for
containers? Are there any other ideas or processes i can try out?
You can create a sparse file,
I've specified a bind mount for my container in my lxc.conf, but I
don't see it in my container's /proc/mounts. This is the mount.entry
from my lxc.conf:
lxc.mount.entry = /tmp/foo /var/lib/lxc/rootfs/default/mnt/master2 none bind 0 0
(full lxc.conf:
After posting this, I thought to change the mount point which solved
my problem. I think the issue was I put the mount point under
/mnt/master2 (moving it to /master2 worked)
Why would putting my mount under /mnt prevent it from being seen by
the container?
On Fri, Jan 7, 2011 at 6:04 PM, Ryan
The instructions that I've seen for LXC suggest creating a bridge in the
host, placing its name in lxc.network.link.
On a diskless system I have eth0 eth1, and create the bridge on eth1.
I can't put eth0 in a bridge, because it's the port for the NFS root.
But when I want traffic to go from
