Yepp, and that's IMHO a design flaw. E.g. if one wants to distribute the
load on iots storage, it might make sense, to distribute the zones of
several storage devices, e.g. zone1 on JBOD1, zone2 on JBOD2, etc
As said, the only thing, which lxc nees to track is a single "config
directory" which
All the LXC commands default to tracking a single lxcpath which is
/var/lib/lxc or whatever you set as lxc.lxcpath in /etc/lxc/lxc.conf
It is actually a feature that LXC will not attempt to keep track of
containers outside that path because that's what we expect other
container managers (like LXD)
** Package changed: upstart (Ubuntu) => lxc (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1424233
Title:
RFE lxc: lxc should do a better jon of housekeeping containers
To man
