Apparmor denies bind to abstract unix sockets such as @/var/lib/juju/mutex-/store-lock

Bug #1604967 reported by Nicholas Skaggs
16
This bug affects 3 people
Affects Status Importance Assigned to Milestone
Canonical Juju
Confirmed
Low
Unassigned
snapd
Fix Released
High
Jamie Strandboge

Bug Description

After snapping up the juju client, attempting to perform a bootstrap gives me:

Log: apparmor="DENIED" operation="bind" profile="snap.juju.juju" pid=11972 comm="juju" family="unix" sock_type="stream" protocol=0 requested_mask="bind" denied_mask="bind" addr="@/var/lib/juju/mutex-/store-lock"

tags: added: snapd-interface
summary: - Apparmor denies bind to /var/lib/juju/mutex-/store-lock
+ Apparmor denies bind to abstract unix sockets such as
+ @/var/lib/juju/mutex-/store-lock
Changed in snappy:
status: New → Triaged
importance: Undecided → High
assignee: nobody → Jamie Strandboge (jdstrand)
tags: added: conjure
Revision history for this message
Nicholas Skaggs (nskaggs) wrote :

Jamie, what's the status on this?

Revision history for this message
Jamie Strandboge (jdstrand) wrote :

@Nicholas, planned but not implemented yet. It was deprioritized to make room for various GA work but is starting to bubble up to the top of the queue again.

Revision history for this message
Jamie Strandboge (jdstrand) wrote :

Is this still an issue for the juju snap?

Changed in snappy:
status: Triaged → Incomplete
affects: snappy → snapd
Revision history for this message
Adam Stokes (adam-stokes) wrote :

Yes this is still an issue with juju confined snaps

Zygmunt Krynicki (zyga)
Changed in snapd:
status: Incomplete → Triaged
Revision history for this message
Zygmunt Krynicki (zyga) wrote :

Is this an issue with apparmor proper or with snapd's use of apparmor for interfaces and confinement in general? Do we need to add a rule to one of the existing interfaces? Is this a new interface for juju specifically?

Changed in snapd:
status: Triaged → Incomplete
Revision history for this message
Jamie Strandboge (jdstrand) wrote :

FYI, I detailed some of what this might look like here: https://forum.snapcraft.io/t/how-to-use-dbus-run-session-on-ubuntu-core/7077/2 (where we allow snaps to create abstract sockets at @snap.SNAP_NAME.**). This concept could be extended in a similar fashion as the dbus interface, where it might be called 'socket' with a declared name that requires a snap declaration to use the name (that interface I would think would support both abstract and named sockets).

Changed in snapd:
status: Incomplete → Triaged
Revision history for this message
Tim McNamara (tim-clicks) wrote :

Adding Juju as an affected project as this bug affects our ability to use strict confinement for our snaps.

Changed in juju:
status: New → Confirmed
Revision history for this message
Zygmunt Krynicki (zyga) wrote :

Jamie's post https://forum.snapcraft.io/t/how-to-use-dbus-run-session-on-ubuntu-core/7077/2 seems to indicate that this was fixed in 2.36

I'm marking it as fixed released. Please reopen if there is something specific that is also needed.

Changed in snapd:
status: Triaged → Fix Released
Revision history for this message
Canonical Juju QA Bot (juju-qa-bot) wrote :

This bug has not been updated in 2 years, so we're marking it Low importance. If you believe this is incorrect, please update the importance.

Changed in juju:
importance: Undecided → Low
tags: added: expirebugs-bot
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.