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 either contains the symlinks to the "real" zone configs OR the real config fails itself - since they usually contain lxc.rootfs = ..., there is not really a need, to keep it in its original place. And last but not least, IMHO LXC should have an interest to make things easy to manage for the users, otherwise there is no wonder, why everyone is talking about docker but not about lxc ... -- 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 manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1424233/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
