Sorry for taking so long to get back to you on this.
> Alistair Young (2021-05-07):
> > Specifically, systemd-detect-virt detects WSL as a container,
> > technically accurately, but this then causes the apparmor.systemd
> > script to decline to start apparmor.
>
> I'm trying to understand what's,
Unfortunately I have not had the time to work on this as I intended to, and as
has been pointed out, .NET 5.0 is now released. I’m therefore closing this ITP.
Apologies to anyone anticipating the package.
Control: tags -1 + fixed-upstream
From intrigeri (2022-02-12):
> intrigeri (2022-02-12):
> > Christian Boltz (2021-11-08):
> >> Your patch looks like something that should (also?) be fixed upstream.
> >
> > My understanding is that the problem here is caused by a Debian patch:
>
> True, but stil
> If I understand correctly, this is a problem with WSL 1 that will go away with
> WSL 2, because WSL 1 is a compatibility layer in which the Windows kernel
> pretends to be Linux (like Wine in reverse), but WSL 2 is a virtual machine
> running a real Linux kernel (suitable for e.g. systemd)?
No,
An improved patch for this issue follows, in accordance with the above thread:
--- rc.apparmor.functions 2021-11-08 13:27:06.461249682 -0600
+++ rc.apparmor.functions 2021-11-08 13:30:05.766141212 -0600
@@ -68,7 +68,7 @@
# something like `systemd-detect-virt --container`.
#
# The on
5 matches
Mail list logo
