Dear Friends
I am using the latest version of LXC
rpm -qa | grep lxc
lxc-devel-1.0.3-1.fc20.x86_64
libvirt-daemon-driver-lxc-1.1.3.4-4.fc20.x86_64
lxc-libs-1.0.3-1.fc20.x86_64
lxc-1.0.3-1.fc20.x86_64
lxc-debuginfo-1.0.3-1.fc20.x86_64
systemctl start lxc.service
- Unit lxc.service has begun sta
On Wed, 2014-04-30 at 14:46 -0400, CDR wrote:
> I know how to autostart a libvirt LXC container with the machine, but
> have not found how to do the same with pure LXC containers. I don't
> mean the hard way, writing a systmd service. I mean simpler way.
> Any idea?
What version of LXC are you run
On Wed, Apr 30, 2014 at 02:46:57PM -0400, CDR wrote:
> I know how to autostart a libvirt LXC container with the machine, but
> have not found how to do the same with pure LXC containers. I don't
> mean the hard way, writing a systmd service. I mean simpler way.
> Any idea?
lxc.start.auto = 1
--
I know how to autostart a libvirt LXC container with the machine, but
have not found how to do the same with pure LXC containers. I don't
mean the hard way, writing a systmd service. I mean simpler way.
Any idea?
___
lxc-users mailing list
lxc-users@lists
No, I don't use apparmor or selinux.
I went past the error by starting the top level container as pure LXC,
not libvirt. To my surprise, Libvirt nat networking does work inside a
LXC container, but not in a Libvirt one.
I a now about to start the second level container and see if the theory works.
Quoting CDR (vene...@gmail.com):
> Dear Friends
> I defined a new network for libvirtd, after the default network gave
> me the same error:
>
> virsh net-start nat
> error: Failed to start network nat
> error: Unable to set bridge nat0 forward_delay: Read-only file system
Do you have apparmor ena
Quoting Daniel P. Berrange (berra...@redhat.com):
> On Wed, Apr 30, 2014 at 09:01:56AM -0400, CDR wrote:
> > I need to provide NAT networking to my LXC containers, much like using
> > virbr0 from libvirt, except that nesting a libvirt-lxc container does
> > not work. So if I nest a pure LXC contain
"Or you could just tell lxc tools to connect the container
to the virbr0 device that libvirt already provided."
That was exactly my idea. I created a libvirt Fedora 20 container,
installed libvirt and lxc inside, created a pure LXC container and
tried to connect its network to virbr0. Except that w
On Wed, Apr 30, 2014 at 09:01:56AM -0400, CDR wrote:
> I need to provide NAT networking to my LXC containers, much like using
> virbr0 from libvirt, except that nesting a libvirt-lxc container does
> not work. So if I nest a pure LXC container, which is supported, how
> would you create a bridge th
Dear Daniel
I am not nesting libvirt-containers. I create a top libvirt container
and inside a use pure LXC, the "nested" container is LXC. I do this
only to get virbr0 so my inner-most container gets access to
nat-networking.
Is this impossible?
On Wed, Apr 30, 2014 at 6:00 AM, Daniel P. Berrange
I need to provide NAT networking to my LXC containers, much like using
virbr0 from libvirt, except that nesting a libvirt-lxc container does
not work. So if I nest a pure LXC container, which is supported, how
would you create a bridge that would nat-forward the packets to the
network?
I am sure it
On Wed, Apr 30, 2014 at 12:10:41AM -0400, CDR wrote:
> I need to solve a business issue that it can be solved easily if I create
> an LXC Fedora container and inside I create another container.
> Will that work or I am dreaming?
FYI, the libvirt LXC driver is not the same as the sf.net LXC toolcha
Hi:
Stéphane Graber has a great blog post series where he includes this feature
(Container nesting)
https://www.stgraber.org/2013/12/21/lxc-1-0-advanced-container-usage/
---
JuanFra Rodriguez Cardoso
Redoop Core Team
On Wed, Apr 30, 2014 at 6:10 AM, CDR wrote:
> I need to solve a business i
13 matches
Mail list logo
