touch-packages team mailing list archive

[Serge Hallyn <1384327@xxxxxxxxxxxxxxxxxx>]

I'm saying this is not a bug because the limited path is by design.  Your
system in fact is telling lxc which path to use as the default.

If you think that rather than take the value from the system through sysconf,
we should always use a longer PATH, then that could be discussed on the
lxc-devel mailing list.

Really to me the bug seems to be that sysconf(_SC_PATH) on ubuntu isn't giving
the path that root gets by default.

-- 
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:
  Invalid

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