snap install --classic juju fails

[Paul Gear]

Trying to install the juju snap on zesty amd64 fails:

root@peleg:~# snap install --classic juju
error: cannot perform the following tasks:
- Run configure hook of "juju" snap if present (run hook "configure": cannot change profile for the next exec call: No such file or directory)

Full typescript at http://pastebin.ubuntu.com/25160880/

Juju 2.2.2 installs and works fine via apt.

[Christopher Lee (veebers)]

I created a fresh zesty lxd container (installed squashfuse to let snap work in a container) and tried to install juju as per commented in the bug and it installs fine for me.

Possibly a snap bug? (or as Paul mentioned in IRC could be the config script + network setup)

[Michael Vogt (mvo)]

What is the output of: "snap version" on the system where this fails? Fwiw, it works fine on my 2.26.14 based machine. So any hint on what I can do to reproduce is appreciated.

[Zygmunt Krynicki (zyga)]

I think this is related to the lxd container. Can you tell me if it has apparmor stacking enabled or runs unconfined? The error message (cannot change profile for the next exec call: No such file or director) seems to say that snap-confine cannot change the apparmor profile for during the exec call. This implies writing to /proc/$PID/attr/exec so maybe the container limits (in whatever way) access to procfs?

[John A Meinel (jameinel)]

If you are installing snaps in an LXD container, you also need to make sure
you have squashfuse installed (and possibly also 'fuse' as there may be a
problem with the dependencies).
They were looking to add those into the default images (since snapd is also
there), but its possible your image is older than that.

John
=:->

On Tue, Jul 25, 2017 at 5:41 PM, Zygmunt Krynicki <
<email address hidden>> wrote:

> I think this is related to the lxd container. Can you tell me if it has
> apparmor stacking enabled or runs unconfined? The error message (cannot
> change profile for the next exec call: No such file or director) seems
> to say that snap-confine cannot change the apparmor profile for during
> the exec call. This implies writing to /proc/$PID/attr/exec so maybe the
> container limits (in whatever way) access to procfs?
>
> --
> You received this bug notification because you are subscribed to juju.
> Matching subscriptions: juju bugs
> https://bugs.launchpad.net/bugs/1705988
>
> Title:
> snap install --classic juju fails
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/juju/+bug/1705988/+subscriptions
>

[Paul Gear (paulgear)]

root@peleg:~# snap version
snap 2.26.9
snapd 2.26.9
series 16
ubuntu 17.04
kernel 4.12.0-041200-generic
root@peleg:~# snap list
Name Version Rev Developer Notes
core 16-2.26.9 2381 canonical -
root@peleg:~# snap refresh
All snaps up to date.

No containers were harmed (or used) in the creation of this bug report. :-)

[Paul Gear (paulgear)]

Maybe this is related to the fact that I'm running a generic kernel? (The zesty kernels are unstable on my machine.)

[Mark Shuttleworth (sabdfl)]

AIUI there a a few AppArmor patches that have not yet landed upstream,
for confinement. For the rest, vanilla latest upstream should work, most
of the things snapd requires have landed.

Mark

[Zygmunt Krynicki (zyga)]

I'm switching this bug to incomplete because the last update was over two years ago. Dear reporter, can you please look at assessing this issue again? Is it still a problem?

[Launchpad Janitor (janitor)]

[Expired for juju because there has been no activity for 60 days.]

[Launchpad Janitor (janitor)]

[Expired for snapd because there has been no activity for 60 days.]

[Launchpad Janitor (janitor)]

[Expired for snapd (Ubuntu) because there has been no activity for 60 days.]