** Description changed: - 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. + == 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.
-- 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/1517107 Title: $PATH is getting clobbered when starting a container with Upstart To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1517107/+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
