Public bug reported:

Intro:
Currently dnsmasq profile includes extra rights for lxd. Current 
usr.sbin.dnsmasq profile works with current lxd from xenial repository. But in 
lxd git (available in lxd-git-master ppa now) version network api was 
introduced, and since lxd quite active, is not too long since new lxd will be 
xenial repository. And that means people will lose network in all containers in 
production in future. This could be fixed with this extra rule in 
usr.sbin.dnsmasq profile:
/var/lib/lxd/networks/** rw, 
in usr.sbin.dnsmasq profile.

1) Ubuntu 16.04.1 LTS

2) apparmor-profiles (currently 2.10.95-0ubuntu2.4). I couldn't select
apparmor-profiles, only apparmor or apparmor-profiles-extra. Don't know
why, mb launchpad bug.

3) What you expected to happen:
network in lxd will start 

4) apparmor usr.sbin.dnsmasq profile blocks network in new lxd version

Bug original source:
https://github.com/lxc/lxd-pkg-ubuntu/issues/21

** Affects: apparmor (Ubuntu)
     Importance: Undecided
         Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/1631409

Title:
  Update usr.sbin.dnsmasq profile for network api in lxd

Status in apparmor package in Ubuntu:
  New

Bug description:
  Intro:
  Currently dnsmasq profile includes extra rights for lxd. Current 
usr.sbin.dnsmasq profile works with current lxd from xenial repository. But in 
lxd git (available in lxd-git-master ppa now) version network api was 
introduced, and since lxd quite active, is not too long since new lxd will be 
xenial repository. And that means people will lose network in all containers in 
production in future. This could be fixed with this extra rule in 
usr.sbin.dnsmasq profile:
  /var/lib/lxd/networks/** rw, 
  in usr.sbin.dnsmasq profile.

  1) Ubuntu 16.04.1 LTS

  2) apparmor-profiles (currently 2.10.95-0ubuntu2.4). I couldn't select
  apparmor-profiles, only apparmor or apparmor-profiles-extra. Don't
  know why, mb launchpad bug.

  3) What you expected to happen:
  network in lxd will start 

  4) apparmor usr.sbin.dnsmasq profile blocks network in new lxd version

  Bug original source:
  https://github.com/lxc/lxd-pkg-ubuntu/issues/21

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to     : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to