touch-packages team mailing list archive

[Jens Elkner <1424233@xxxxxxxxxxxxxxxxxx>]

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
Touch seeded packages, 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

Status in lxc package in Ubuntu:
  Won't Fix

Bug description:
  Right now lxc does a pretty poor job wrt. managing containers, i.e.
  one needs to know, where containers have been installed to be able to
  access/use/manage them (option -P dir) unless they've been installed
  in the default location. Even if one knows the install path, it is
  still a pain to work with corresponding lxc commands, because one
  always needs to specify -P ...

  This really sucks (especially if one needs to service foreign
  machines).

  So the proposal is, that if a zone gets created, lxc puts a symlink to
  the related config under /etc/lxc/cfg/ or something like that and all
  lxc tools like lxc-ls first check this directory, and if the link
  destination exists, it has all information it needs to know., i.e. all
  "-P idontknow" madness is not required anymore.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1424233/+subscriptions