-
Notifications
You must be signed in to change notification settings - Fork 1.2k
Anbox Couldn't work on lxc 4.0.8 #1801
Comments
Checking journalctl on my own after starting anbox-session-manager also shows this:
|
downgrading lxc to 1:4.0.6-1 temporarily solves the problem |
Here is the core dump. |
Can confirm, downgrading lxc to 1:4.0.6-1 solves the problem in Manjaro. |
Depends on your kernel version.
Could fix it however I can't still start the container.. |
Arch is already on lxc 4.0.9, and that also does not work w/ anbox |
I managed to get anbox working under Fedora 34. A dirty patch (not suitable for submitting and will break with older lxc versions or a different GNU/Linux distro which uses apparmor): There is also an issue with newer versions of lxc: |
Unfortunately the "fix" that supposedly solved this issue that got merged into lxc does not in fact fix the problem. I just tried with the latest lxc master and it's the exact same error. |
have you also tried applying this patch to anbox? I need to patch both lxc and anbox to get it working here. |
Ah, you'd said on the lxc MR that just that patch fixed the issue. Unfortunately I'm on Arch which uses apparmor for snapd, so I guess that patch won't work, correct? I can still give it a try though, I have a 5900X so it's not like compiling anbox is a big commitment. |
Well turns out apparmor isn't an issue for me. I just patched it and built anbox and sure enough, it works. Thanks a lot, it's appreciated. |
Can anybody please test #1827 and report results? I believe that should fix this (although it does not solve the issue with anbox not supporting cgroupsv2 for lxc). @CecilHarvey, which is the reason you did this change? Is that also related to LXC 4.0.9? - set_config_item(lxc_config_apparmor_profile_key, "unconfined");
+ //set_config_item(lxc_config_apparmor_profile_key, "unconfined"); |
Please check that no similar bug is already reported. Have a look on the list of open bugs at https://github.com/anbox/anbox/issues
Make sure you are running the latest version of Anbox before reporting an issue. Update snap to latest:
snap refresh --devmode --edge anbox
Make sure you have debug logs enabled:
sudo snap set anbox debug.enable=true
Reproduce the error while debug logs enabled.
Run the anbox logs collection utility and attach the tar file.
sudo /snap/bin/anbox.collect-bug-info
** Please paste the result of
anbox system-info
below:**anbox system-info output
Please describe your problem:
When I using latest anbox from ArchLinux(AUR), I followed ArchWiki's guidance, however, I have got this problem
when using
$ anbox launch --package=org.anbox.appmgr --component=org.anbox.appmgr.AppViewActivity
:Then I pressed
$ anbox session-manager
, it outputed:What were you expecting?:
I hope someone could fix it.
Additional info:
I'm Using
lxc-1:4.0.8-1
maybe the latest anbox haven't support it.The text was updated successfully, but these errors were encountered: