Your message dated Tue, 23 Jul 2024 19:21:07 +0800
with message-id <[email protected]>
and subject line Re: [pkg-lxc-devel] Bug#1031374: lxc: apparmor
sock_type="dgram" denied
has caused the Debian Bug report #1031374,
regarding lxc: apparmor sock_type="dgram" denied
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
1031374: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1031374
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: lxc
Version: 1:5.0.2-1
Severity: normal
X-Debbugs-Cc: [email protected]
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
I see a lot of apparmor error messages like this, I want to know, how to
allow/deny it (mute this "unix socket file_lock" error message), thanks.
2023-02-16T06:51:06.656725+08:00 dmz103 kernel: [32682.801651] audit: type=1400
audit(1676501466.649:142): apparmor="DENIED" operation="file_lock"
profile="lxc-container-default-cgns-local" pid=14515 comm="(crub_all)"
family="unix" sock_type="dgram" protocol=0 requested_mask="send"
kaka@dmz103:~$ uname -a
Linux dmz103 6.1.0-4-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.11-1 (2023-02-09)
x86_64 GNU/Linux
* What led up to the situation?
* What exactly did you do (or not do) that was effective (or
ineffective)?
* What was the outcome of this action?
* What outcome did you expect instead?
*** End of the template - remove these template lines ***
-- System Information:
Debian Release: bookworm/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 6.1.0-4-amd64 (SMP w/2 CPU threads; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages lxc depends on:
ii debconf [debconf-2.0] 1.5.82
ii dnsmasq-base [dnsmasq-base] 2.89-1
ii iproute2 6.1.0-1
ii iptables 1.8.9-2
ii libapparmor1 3.0.8-3
ii libc6 2.36-8
ii libcap2 1:2.66-3
ii libgcc-s1 12.2.0-14
ii liblxc-common 1:5.0.2-1
ii liblxc1 1:5.0.2-1
ii libseccomp2 2.5.4-1+b3
ii libselinux1 3.4-1+b5
ii nftables 1.0.6-2
ii sysvinit-utils [lsb-base] 3.06-2
Versions of packages lxc recommends:
ii apparmor 3.0.8-3
pn debootstrap <none>
ii dirmngr 2.2.40-1
ii gnupg 2.2.40-1
pn libpam-cgfs <none>
ii lxc-templates 3.0.4.48.g4765da8-1
ii lxcfs 5.0.3-1
ii openssl 3.0.8-1
ii rsync 3.2.7-1
pn uidmap <none>
ii wget 1.21.3-1+b2
Versions of packages lxc suggests:
ii btrfs-progs 6.1.3-1
ii lvm2 2.03.16-2
ii python3-lxc 1:5.0.0-1+b1
-- Configuration Files:
/etc/default/lxc-net changed:
USE_LXC_BRIDGE="false"
/etc/lxc/default.conf changed:
lxc.net.0.type = veth
lxc.net.0.link = lxcbr30
lxc.net.0.flags = up
lxc.apparmor.profile = generated
lxc.apparmor.allow_nesting = 0
-- debconf information:
* lxc/auto_update_config: false
--- End Message ---
--- Begin Message ---
On 7/23/24 4:08 PM, Mathias Gibbens wrote:
Control: retitle -1 lxc: apparmor sock_type="dgram" denied
Looks like the same issue as reported in #1050256, #1038315,
#1042880, and #1052934.
Mathias
Thanks Mathias.
Yes, it no longer an issue after running on new kernel, so I close it.
John.
--- End Message ---
