Comment # 25 on bug 1214845 from Eric van Blokland
(In reply to James Fehlig from comment #24)
> (In reply to Eric van Blokland from comment #23)
> > I'm fully aware that the LXC driver is not supported by SUSE and that I have
> > you to thank for any patches that get applied regardless. This is also why I
> > don't mind to spend some time to fix issues and actually submit a patch.
> 
> Thanks for that!
> 
> > As to the why "libvirt-lxc": I've worked with libvirt my entire professional
> > life to run vms. So it's tech that I know (that's why libvirt). For
> > situations where an entire vm is a bit overkill I prefer to use containers.
> > The fact I can use the same cli and ui tools for both my vms and containers
> > is extremely appealing.
> 
> Right, one of the main benefits of libvirt. Okay, I'll leave the lxc driver
> enabled with the caveat that user community is also the maintainers of the
> driver :-). I'll encourage bug reporters to pursue a fix upstream, at which
> point I'm happy to integrate in the downstream package.
> 
> > Is there another libvirt container driver that would be more or less a drop
> > in replacement for LXC? I see a few others listed, but I'm not familiar with
> > them and apparently can't assume they're actively maintained.
> 
> lxc is the only container driver for libvirt.

Sorry for not replying earlier, I've been crazy busy. I don't mind doing some
maintenance for the software I use.

I will try to fix the issue in this report as soon I can, but since there are a
couple of workarounds, it's not on the top of my todo list at this time.

Is there anyone in particular you think I could bother if I have questions
about implementation details?


You are receiving this mail because: