Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.devel.testing > #1307

Bug#990140: upgrade-reports: lxc-attach does not start with apparmor problem after ugrade to 10.10

Cross-posted to 3 groups.

Show key headers only | View raw

[Multipart message — attachments visible in raw view] - view raw

Hi Bernd,

Thanks for your report.

On 21-06-2021 18:04, Bernd Breuer wrote:
> after the recent upgrade to Buster 10.10 (including a kernel upgrade) the command 'lxc-attach' (out of the Linux Container (lxc) set of commands), typed in like
> 
> "sudo lxc-attach <container-name>"
> 
> stopped working with the error message
> 
> "lxc-attach: <container-name>: lsm/lsm.c: lsm_process_label_set_at: 174 Operation not permitted - Failed to set AppArmor label "unconfined"
> 
> The conainer itself is starting, but apparmor related config lines like
> 
> "lxc.apparmor.profile = unconfined"
> 
> produce the above mentioned error, also on another machine after the
> same packages upgrade.
> 
> I expect lxc-attach to provide me a root shell in the running lxc-container like  it was the case before the recent upgrade.

As we didn't upgrade lxc during the point release, this *may* be caused
by the updated Linux kernel. What happens if you reboot using the
previous kernel?

Paul

Back to linux.debian.devel.testing | Previous | Next — Previous in thread | Find similar

Thread

Bug#990140: upgrade-reports: lxc-attach does not start with apparmor problem after ugrade to 10.10 Bernd Breuer <b.breuer@gmx.de> - 2021-06-21 18:10 +0200
  Bug#990140: upgrade-reports: lxc-attach does not start with apparmor problem after ugrade to 10.10 Paul Gevers <elbrus@debian.org> - 2021-06-21 19:10 +0200

csiph-web