touch-packages team mailing list archive

[Rolf Leggewie <1177412@xxxxxxxxxxxxxxxxxx>]

raring has seen the end of its life and is no longer receiving any
updates. Marking the raring task for this ticket as "Won't Fix".

** Changed in: lxc (Ubuntu Raring)
       Status: Fix Committed => Won't Fix

-- 
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/1177412

Title:
  lxc-ls doesn't show nested containers when using an alternate lxc path

Status in lxc package in Ubuntu:
  Fix Released
Status in lxc source package in Raring:
  Won't Fix

Bug description:
  == Rationale ==
  "lxc-ls -P /some/path --fancy --nesting" fails to show nested containers and running container information.
  This is caused by the lack of lxcpath awareness in the get_ips() API call and by the NESTED environment variable containing the host's lxcpath and not the container's default lxcpath.

  == Test case ==
  1) Create a container with a sub-container in it
  2) Move the container to an alternate path, let's say /tmp/lxc
  3) Start it with: lxc-start -P /tmp/lxc -n container -d
  4) List the containers: lxc-ls --fancy --nesting -P /tmp/lxc

  Expected output is the main container with the sub-container under it,
  both of which with their status and IP addresses.

  == Regression potential ==
  This slightly changes the behaviour of lxc-ls in that in the past it'd successfully list sub-containers if they had the exact same custom lxcpath as the host, however this is very unusual and not something upstream feels should be supported at this time.
  Instead it's expected that the container containing sub-containers in the default lxcpath will be much more common.

  As the get_ips() call was preventing those containers to show up
  anyway, it's unlikely anyone will notice the small change in
  behaviour.

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