New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
net_cls interfering with lxd #3651
Comments
Pleas see #3660. We have added more documentation on this now. |
@faern thanks! though would you be able to hint at where I should mount it to, so it doesn't interfere with v2? |
Technically any directory will work - any reasonable consumer of the old controller should be able to find it anywhere. If you believe our daemon will be the only user of the old controller, it'd be reasonable to mount it in |
@pinkisemils does that mean that net_cls is v1 only? so wherever I will mount it to, it'll taint v2 groups and make it mixed again? |
Yes. |
I guess you can't use LXD/LXC together with mullvad-exclude then, that's unfortunate, is there any workarounds for this to still be able to keep using both? |
I've gotten it working by just mounting the |
oh wow I wasn't aware it can literally be mounted anywhere, will try that shortly, thanks! |
that worked, thanks so much! |
Given that AIUI the mountpoint is arbitrary, can't the default be changed so that it doesn't interfere with LXD? |
Issue report
Operating system: Arch Linux (5.18.3-zen1-1-zen)
App version: 2022.2-beta2
Issue description
mullvad automatically mounts what I assume is a v1 cgroup for net_cls, causing lxd to not be able to start containers as it now thinks it's an unsupported/broken cgroup host, unmounting net_cls makes mullvad-exclude (obviously) not work with
No net_cls controller
reading #1893 supposedly there's some device setting you can do, to mount net_cls elsewhere? but I could not find such setting anywhere in the beta app, what's the solution to avoid having it break lxd?
The text was updated successfully, but these errors were encountered: