touch-packages team mailing list archive

[Simon Déziel <1384327@xxxxxxxxxxxxxxxxxx>]

On 10/23/2014 12:27 AM, Serge Hallyn wrote:
> As such, I think it would be pretty reasonable to change lxc to always
> use its own path.

Serge, thanks for looking into this!

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

Title:
  lxc-attach --clear-env results in a limited $PATH in the container

Status in “lxc” package in Ubuntu:
  Triaged

Bug description:
  Here is the problem in more details:

   # Clearing the env
   $ printf 'echo $PATH\n' | sudo lxc-attach --clear-env -n p1
   /bin:/usr/bin

   # Keeping the env
   $ printf 'echo $PATH\n' | sudo lxc-attach --keep-env -n p1
   /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin

  While keeping the env seems like a good workaround it cause other
  undesirable effects like preserving $HOME that doesn't (always) exist
  in the container.

  Additional information:

  $ apt-cache policy lxc
  lxc:
    Installed: 1.0.6-0ubuntu0.1
    Candidate: 1.0.6-0ubuntu0.1
    Version table:
   *** 1.0.6-0ubuntu0.1 0
          500 http://archive.ubuntu.com/ubuntu/ trusty-proposed/main amd64 Packages
          100 /var/lib/dpkg/status
       1.0.5-0ubuntu0.1 0
          500 http://archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages
       1.0.3-0ubuntu3 0
          500 http://archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages

  Both host and container are:

  $ lsb_release -rd
  Description:	Ubuntu 14.04.1 LTS
  Release:	14.04

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