Hello,
I have Fedora 32 users reporting that after installing the app using its snap package (snapcraf.yaml) and run it they get:
cgroup v2 is not fully supported yet, proceeding with partial confinement
Does anyone know why this is happening and how it could be resolved?
Thanks!
It’s a warning that snapd cannot fully confine the application because the OS uses cgroups V2 but snapd doesn’t completely support that yet. This seems like the kind of warning users should get when installing the package, not when running it.
As @galgalesh said, you can ignore the cgroups warning. Support for cgroups v2 is in development, but has not been rolled out.
The cause of the sudo error is that /snap/bin is not in sudo’s secure_path configuration variable on Fedora, so it does not find your auto-cpufreq executable. You should be able to run sudo /snap/bin/auto-cpufreq or sudo snap run auto-cpufreq instead.
Alternatively you could try adding /snap/bin to the path by running sudo visudo and change the path.
Thank you both for your valuable input, much appreciated. I’ll make this as a note to Fedora users who install an app as a snap.
Do you know if there’s a link to a Github/Launchpad issue where I could monitor development of support for cgroups v2?
And finally do you think it’s a good idea to suggest to Fedora users to disable cgroups v2 as a workaround to this problem, i.e:
sudo grubby --update-kernel=ALL --args="systemd.unified_cgroup_hierarchy=0"
Disabling the cgroups unified hierarchy would not solve your sudo problem, so no I wouldn’t suggest you tell people to do that. The Fedora developers test their system in the unified hierarchy mode, so changing the setting might cause other things to break or function sub-optimally.
This is the PR where the cgroups v2 support is being worked on:
Perfect, again thanks for your input @jamesh