Dear LXC maintainers,
johnw:
> I think it's not bug.
> Because I removed systemd, either if I reinstall systemd, or I add
> some mount rules to apparmor , then the denied messages gone.
Given my own test results and John's feedback, I suggest closing
this bug.
Cheers,
--
intrigeri
Hi, sorry for late reply,
I think it's not bug.
Because I removed systemd, either if I reinstall systemd, or I add some mount
rules to apparmor , then the denied messages gone.
Thank you for help, thanks.
On 2018年10月26日 下午5:55:02 [GMT+08:00], intrigeri wrote:
>Control: tag -1 - upstream
Control: tag -1 - upstream
Control: tag -1 + moreinfo
Hi,
kaka:
> Over the year, if I enable apparmor for lxc (lxc.aa_profile =
> lxc-container-default),
First, I don't think you need to turn this on manually and I doubt
this is the best AppArmor profile to use. According to
Control: tag -1 + upstream
Hi,
johnw:
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=898025
> Over the year, if I enable apparmor for lxc (lxc.aa_profile =
> lxc-container-default),
> I see a lot of "apparmor denied" messages like below,
> But the lxc itself is can running and functional
-- Configuration Files:
/etc/apparmor.d/abstractions/lxc/container-base [Errno 13] Permission
denied: '/etc/apparmor.d/abstractions/lxc/container-base'
/etc/apparmor.d/abstractions/lxc/start-container [Errno 13] Permission
denied: '/etc/apparmor.d/abstractions/lxc/start-container'
Package: lxc
Version: 1:2.0.9-6
Severity: normal
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
* What exactly did you do (or not do) that was effective (or
ineffective)?
* What was the outcome of
6 matches
Mail list logo
