PATH is not set after namespace is initialized

[Federico Gimenez]

This happens in a amd64 image using the classic snap from edge in devmode, this are the snap versions:

test@localhost:~$ snap list
Name Version Rev Developer Notes
classic 16.04 15 canonical devmode
core 16.04.1 15 canonical -
pc 16.04-0.8 9 canonical -
pc-kernel 4.4.0-38-1 21 canonical -

When trying to execute classic commands this is the output:

test@localhost:~$ sudo classic "sudo apt update && apt install -y git golang-go"
Creating classic environment
test@localhost:~$ sudo classic "sudo apt update && apt install -y git golang-go"
cannot open mount namespace file for namespace group classic. errmsg: Permission denied

[Zygmunt Krynicki (zyga)]

This is fixed by the following pull request: https://github.com/snapcore/snap-confine/pull/162

[Andy Whitcroft (apw)]

Hello Federico, or anyone else affected,

Accepted snap-confine into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/snap-confine/1.0.43-0ubuntu1~16.04.1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

[Launchpad Janitor (janitor)]

This bug was fixed in the package snap-confine - 1.0.43-0ubuntu1

---------------
snap-confine (1.0.43-0ubuntu1) yakkety; urgency=medium

  * New upstream release (LP: #1630479, LP: #1630492, LP: #1628612)
  * debian/patches/lp1630789.patch: allow running snaps by non-root users in
    LXD containers (LP: #1630789)

 -- Jamie Strandboge <email address hidden> Thu, 06 Oct 2016 12:29:59 +0000

[Federico Gimenez (fgimenez)]

All working fine with a recent core snap version:

fgimenez@localhost:~$ snap version
snap 2.16+ppa35-1
snapd 2.16+ppa35-1
series 16
fgimenez@localhost:~$ snap list
Name Version Rev Developer Notes
classic 16.04 17 canonical devmode
core 16.04.1 72 canonical -
pc 16.04-0.8 9 canonical -
pc-kernel 4.4.0-36-2 19 canonical -
fgimenez@localhost:~$ sudo classic "sudo apt update && apt install -y git golang-go"
Creating classic environment
Parallel unsquashfs: Using 1 processor
10906 inodes (11944 blocks) to write

[===================================================================================================================================================/] 11944/11944 100%

created 8463 files
created 1424 directories
created 2354 symlinks
created 79 devices
created 0 fifos
(Reading database ... 12853 files and directories currently installed.)
Preparing to unpack .../apt_1.2.12~ubuntu16.04.1_amd64.deb ...
Unpacking apt (1.2.12~ubuntu16.04.1) over (1.2.12~ubuntu16.04.1) ...
Selecting previously unselected package locales.
Preparing to unpack .../locales_2.23-0ubuntu3_all.deb ...
Unpacking locales (2.23-0ubuntu3) ...
Setting up apt (1.2.12~ubuntu16.04.1) ...
Setting up locales (2.23-0ubuntu3) ...
Generating locales (this might take a while)...
Generation complete.
Processing triggers for libc-bin (2.23-0ubuntu3) ...
Get:1 http://security.ubuntu.com/ubuntu xenial-security InRelease [94.5 kB]
Get:2 http://archive.ubuntu.com/ubuntu xenial InRelease [247 kB]
Get:3 http://security.ubuntu.com/ubuntu xenial-security/main amd64 Packages [152 kB]
Get:4 http://security.ubuntu.com/ubuntu xenial-security/main i386 Packages [148 kB]
Get:5 http://archive.ubuntu.com/ubuntu xenial-updates InRelease [95.7 kB]
Get:6 http://security.ubuntu.com/ubuntu xenial-security/main Translation-en [62.9 kB]
Get:7 http://security.ubuntu.com/ubuntu xenial-security/universe amd64 Packages [44.4 kB]
Get:8 http://archive.ubuntu.com/ubuntu xenial-backports InRelease [92.2 kB]
Get:9 http://security.ubuntu.com/ubuntu xenial-security/universe i386 Packages [44.4 kB]
Get:10 http://security.ubuntu.com/ubuntu xenial-security/universe Translation-en [26.7 kB]
Get:11 http://security.ubuntu.com/ubuntu xenial-security/multiverse amd64 Packages [1176 B]
Get:12 http://security.ubuntu.com/ubuntu xenial-security/multiverse i386 Packages [1340 B]
Get:13 http://security.ubuntu.com/ubuntu xenial-security/multiverse Translation-en [628 B]
Get:14 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages [1201 kB]
Get:15 http://archive.ubuntu.com/ubuntu xenial/main i386 Packages [1196 kB]
Get:16 http://archive.ubuntu.com/ubuntu xenial/main Translation-en [568 kB]
Get:17 http://archive.ubuntu.com/ubuntu xenial/restricted amd64 Packages [8344 B]
Get:18 http://archive.ubuntu.com/ubuntu xenial/restricted i386 Packages [8684 B]
Get:19 http://archive.ubuntu.com/ubuntu xenial/restricted Translation-en [2908 B]
Get:20 http://archive.ubuntu.com/ubuntu xenial/universe amd64 Packages [7532 kB]
Get:21 http://archive.ubuntu....

[Launchpad Janitor (janitor)]

This bug was fixed in the package snap-confine - 1.0.43-0ubuntu1~16.04.1

---------------
snap-confine (1.0.43-0ubuntu1~16.04.1) xenial-proposed; urgency=medium

  * Backport from 16.10 (LP: #1630040)

snap-confine (1.0.43-0ubuntu1) yakkety; urgency=medium

  * New upstream release (LP: #1630479, LP: #1630492, LP: #1628612)
  * debian/patches/lp1630789.patch: allow running snaps by non-root users in
    LXD containers (LP: #1630789)

snap-confine (1.0.42-0ubuntu3) yakkety; urgency=medium

  * allow snap-confine to mount on /dev/pts/ptmx for LXD with /dev/ptmx
    symlink

snap-confine (1.0.42-0ubuntu2) yakkety; urgency=medium

  * add mmap to AppArmor policy for snap-confine for running snap-confine
    under LXD on 4.8 kernels

snap-confine (1.0.42-0ubuntu1) yakkety; urgency=medium

  * New upstream release
  * Drop patch skip-nsfs-magic-tests-on-old-kernels.patch (applied upstream)

snap-confine (1.0.41-0ubuntu2) yakkety; urgency=medium

  * add skip-nsfs-magic-tests-on-old-kernels.patch to disable NSFS tests on
    kernels older than 3.19 (LP: #1625565)

snap-confine (1.0.41-0ubuntu1) yakkety; urgency=medium

  * New upstream release, full list of issues is available at
    https://launchpad.net/snap-confine/+milestone/1.0.41
  * Drop all patches (included upstream).
  * Add version to apparmor run-time dependency.

snap-confine (1.0.40-1) unstable; urgency=medium

  * New upstream release, full list of issues is available at
    https://launchpad.net/snap-confine/+milestone/1.0.40
  * Drop apparmor profile from the debian/ directory and install it straight
    from upstream package. This is now automatically consistent with package
    configuration prefix.
  * Drop patch: prctl-compatibility.patch(applied upstream)
  * Add directory /var/lib/snapd/void to snap-confine
  * Add patch: 0001-Don-t-shellcheck-files-spread-prepare-script.patch that
    fixes make check due to a mistake upstream.
  * Add patch: 0001-Stop-using-deprecated-readdir_r.patch (LP: #1615615)

snap-confine (1.0.39-1) unstable; urgency=medium

  * New upstream release.
  * Remove d/patches/01_lp1606277.patch, applied upstream.

snap-confine (1.0.38-3) unstable; urgency=medium

  * debian/patches/prctl-compatibility.patch: add shadow definitions for
    compatibility with older kernel headers.
  * drop build-dependency on shellcheck, which is not used at build time
    and doesn't exist in trusty.
  * make ubuntu-core-launcher "arch:any" to workaround an issue in
    rm_conffile which does not deal with changing architectures
  * fix log-observer interface regression (LP: #1606277)

snap-confine (1.0.38-2) unstable; urgency=medium

  * Fix invocations of rm_conffile.
  * Update d/usr.lib.snapd.snap-confine to the latest upstream version to
    ensure content-sharing fully works.

snap-confine (1.0.38-1) unstable; urgency=medium

  * New upstream release.

 -- Jamie Strandboge <email address hidden> Thu, 06 Oct 2016 14:51:26 +0000

[Steve Langasek (vorlon)]

The verification of the Stable Release Update for snap-confine has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.