[Bug 2080358] [NEW] liblxc-common: AppArmor-Profile for /usr/bin/lxc-copy contains rule for lxc-start
Launchpad Bug Tracker
2080358 at bugs.launchpad.net
Thu Sep 12 04:23:57 UTC 2024
You have been subscribed to a public bug by Ubuntu Foundations Team Bug Bot (crichton):
Hi,
liblxc-common 1:5.0.3-2ubuntu7 provides an AppArmor-Profile for /usr/bin/lxc-copy, but the profile file
contains the rule for /usr/bin/lxc-start instead of /usr/bin/lxc-copy. The mistake was introduced in [1], current Debian versions (1:5.0.2-1 and 1:6.0.1-1) are not affected, but Ubuntu 24.04 (noble) is. This
wrong profile file prevents running lxc-copy on my companies Ubuntu 24.04 machines.
Can you please replace the 'lxc-start' by 'lxc-copy' in
/etc/apparmor/usr.bin.lxc-copy or update to Debian's 1:6.0.1-1 or above?
Thanks and kind regards,
Nicolas
[1]: https://salsa.debian.org/lxc-
team/lxc/-/merge_requests/19/diffs?commit_id=a2ad01ca2081c4dd925037253b01fff0499af17e#d7b13f871dc297c7aa81e98c974db1a24f1b016d_0_21
---
Description: Ubuntu 24.04.1 LTS
Release: 24.04
liblxc-common:
Installed: 1:5.0.3-2ubuntu7
Candidate: 1:5.0.3-2ubuntu7
Version table:
*** 1:5.0.3-2ubuntu7 990
990 http://de.archive.ubuntu.com/ubuntu noble/universe amd64 Packages
100 /var/lib/dpkg/status
ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: liblxc-common 1:5.0.3-2ubuntu7
Uname: Linux 6.10.6 x86_64
ApportVersion: 2.28.1-0ubuntu3.1
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: sway
Date: Wed Sep 11 12:37:23 2024
InstallationDate: Installed on 2024-08-26 (16 days ago)
InstallationMedia: Ubuntu 22.04.4 LTS "Jammy Jellyfish" - Release amd64 (20240220)
SourcePackage: lxc
UpgradeStatus: Upgraded to noble on 2024-09-04 (7 days ago)
modified.conffile..etc.init.d.apport: [modified]
mtime.conffile..etc.init.d.apport: 2024-07-22T16:59:07
** Affects: lxc (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug noble patch wayland-session
--
liblxc-common: AppArmor-Profile for /usr/bin/lxc-copy contains rule for lxc-start
https://bugs.launchpad.net/bugs/2080358
You received this bug notification because you are a member of Ubuntu Sponsors, which is subscribed to the bug report.
More information about the Ubuntu-sponsors
mailing list