Hi Paul (2021.10.10_11:59:12_-0700)
> Shouldn't that bug be raised in severity, considering the request you
> are now asking from autopkgtest? I'm not really enthusiastic to add this
> kind of "work around" code for a bug that's already known for 2 years.
> Maybe there should be a warning in snapd
Hi,
On 10-10-2021 20:51, stefa...@debian.org wrote:
> The issue is that snap is warning that it doesn't completely support
> cgroup v2, yet. But it does work.
>
> See #934372 etc.
Shouldn't that bug be raised in severity, considering the request you
are now asking from autopkgtest? I'm not reall
Hi Paul (2021.10.10_18:38:03_+)
> > Unfortunately executing any confined snapped binaries outputs a line on
> > stderr:
> >> WARNING: cgroup v2 is not fully supported yet, proceeding with partial
> >> confinement
>
> Does this happen on all suites? I thought bullseye defaults to cgroup
> v2,
Hi Stefano,
On 10-10-2021 20:06, Stefano Rivera wrote:
> Unfortunately executing any confined snapped binaries outputs a line on
> stderr:
>> WARNING: cgroup v2 is not fully supported yet, proceeding with partial
>> confinement
Does this happen on all suites? I thought bullseye defaults to cgrou
Package: autopkgtest
Version: 5.17
Severity: normal
Tags: patch
lxd is not packaged for Debian at the moment (ITP #768073), so the
common way to install it on Debian is through snapd.
Unfortunately executing any confined snapped binaries outputs a line on
stderr:
> WARNING: cgroup v2 is not fully
5 matches
Mail list logo