touch-packages team mailing list archive

[Launchpad Bug Tracker <1517107@xxxxxxxxxxxxxxxxxx>]

This bug was fixed in the package lxc - 1.1.5-0ubuntu3

---------------
lxc (1.1.5-0ubuntu3) xenial; urgency=medium

  * Cherry-pick from upstream:
    - Fix preserve_ns to work on < 3.8 kernels. (LP: #1516971)
    - Fix process title rewrite to not mangle the environment. (LP: #1517107)

 -- Stéphane Graber <stgraber@xxxxxxxxxx>  Wed, 18 Nov 2015 13:30:41
-0500

** Changed in: lxc (Ubuntu Xenial)
       Status: Fix Committed => Fix Released

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

Title:
  $PATH is getting clobbered when starting a container with Upstart

Status in lxc package in Ubuntu:
  Fix Released
Status in lxc source package in Vivid:
  Fix Committed
Status in lxc source package in Wily:
  Fix Committed
Status in lxc source package in Xenial:
  Fix Released

Bug description:
  == SRU ==
  Rationale: LXC 1.1 and higher mangles the process env to be able to re-title itself, breaking the environment for sub-processes in the process
  Test case: Spawn a container and check /proc/self/environ
  Regression potential: Worst case scenario is we stamp on a different part of the process memory leading to similar but different breakage. It's been tested not to be the case though, change comes from upstream.

  == Original bug report ==
  I have a script using the Python3 LXC API that starts up a container.  If I use an Upstart job to call the script, the $PATH env var is getting clobbered and the container fails to start.

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