anbox-modules VS LXDesktop

While messing around with Anbox today, I did something wrong while trying to install the kernel modules and ended up soiling the default kernel. My computer froze up, and had to be force shutdown by holding down the power button. After starting it up again it got stuck on the gray login screen, with no UI elements visible.

I tried using Anbox Android emulation, but when I installed the modules using dkms using this github page, I couldn't start the binder module, and I got this output (I am copying this from syslog): Jan 22 15:38:44 localhost kernel: Could not create tracefs 'binder_return' directory Jan 22 15:38:44 localhost kernel: Could not create tracefs 'binder_command' directory Jan 22 15:38:44 localhost kernel: Could not create tracefs 'binder_unmap_kernel_end' directory Jan 22 15:38:44 localhost kernel: Could not create tracefs 'binder_unmap_kernel_start' directory Jan 22 15:38:44 localhost kernel: Could not create tracefs 'binder_unmap_user_end' directory Jan 22 15:38:44 localhost kernel: Could not create tracefs 'binder_unmap_user_start' directory Jan 22 15:38:44 localhost kernel: Could not create tracefs 'binder_alloc_page_end' directory Jan 22 15:38:44 localhost kernel: Could not create tracefs 'binder_alloc_page_start' directory Jan 22 15:38:44 localhost kernel: Could not create tracefs 'binder_free_lru_end' directory Jan 22 15:38:44 localhost kernel: Could not create tracefs 'binder_free_lru_start' directory Jan 22 15:38:44 localhost kernel: Could not create tracefs 'binder_alloc_lru_end' directory Jan 22 15:38:44 localhost kernel: Could not create tracefs 'binder_alloc_lru_start' directory Jan 22 15:38:44 localhost kernel: Could not create tracefs 'binder_update_page_range' directory Jan 22 15:38:44 localhost kernel: Could not create tracefs 'binder_transaction_failed_buffer_release' directory Jan 22 15:38:44 localhost kernel: Could not create tracefs 'binder_transaction_buffer_release' directory Jan 22 15:38:44 localhost kernel: Could not create tracefs 'binder_transaction_alloc_buf' directory Jan 22 15:38:44 localhost kernel: Could not create tracefs 'binder_transaction_fd_recv' directory Jan 22 15:38:44 localhost kernel: Could not create tracefs 'binder_transaction_fd_send' directory Jan 22 15:38:44 localhost kernel: Could not create tracefs 'binder_transaction_ref_to_ref' directory Jan 22 15:38:44 localhost kernel: Could not create tracefs 'binder_transaction_ref_to_node' directory Jan 22 15:38:44 localhost kernel: Could not create tracefs 'binder_transaction_node_to_ref' directory Jan 22 15:38:44 localhost kernel: Could not create tracefs 'binder_transaction_received' directory Jan 22 15:38:44 localhost kernel: Could not create tracefs 'binder_transaction' directory Jan 22 15:38:44 localhost kernel: Could not create tracefs 'binder_wait_for_work' directory Jan 22 15:38:44 localhost kernel: Could not create tracefs 'binder_read_done' directory Jan 22 15:38:44 localhost kernel: Could not create tracefs 'binder_write_done' directory Jan 22 15:38:44 localhost kernel: Could not create tracefs 'binder_ioctl_done' directory Jan 22 15:38:44 localhost kernel: Could not create tracefs 'binder_unlock' directory Jan 22 15:38:44 localhost kernel: Could not create tracefs 'binder_locked' directory Jan 22 15:38:44 localhost kernel: Could not create tracefs 'binder_lock' directory Jan 22 15:38:44 localhost kernel: Could not create tracefs 'binder_ioctl' directory Jan 22 15:38:44 localhost kernel: debugfs: Directory 'binder' with parent '/' already present! I then compiled my kernel with ashmem and anbox-binder support, but when I tried again, this time I didn't have the binder_linux module, as I built binder into the kernel. anbox-container-manager complained about it, when I tried starting it. Do I need to install the dkms anbox modules again after I built support for anbox-binder? Keep in mind that the only problem is with binder. Ashmem is there and is working all fine, having a proper module and everything. Installing the dkms module is most likely going to mess up ashmem. What should I do?

Step 2: adding kernel( this is because I am getting ppa error) git clone https://github.com/anbox/anbox-modules.git cd anbox-modules sh INSTALL.sh sudo modprobe ashmem_linux sudo modprobe binder_linux sudo reboot

As I checked, the ashmem module seems to be an anbox-modules(https://github.com/anbox/anbox-modules) problem, so I tried to install it, but it failed during the make process.

The answer is that the Anbox developers are uncooperative tools who recommend recompiling your kernel from source like it's 2010 if you're later than kernel 5.7 (where kallsyms_lookup_name was removed instead of fixing it, and somebody had to fork their repo.

Significantly easier to get the modules (binder and ashmem) built properly as per this thread. https://github.com/anbox/anbox-modules/issues/75

Well, I have never work with a linux kernel before but I wanted to have Ambox on fedora, I have a dualboot with windows just to use Bluestack! so I though maybe I can use Ambox, when I tried to install it I ran into a few problems, first I tried to follow the instrutions on https://github.com/anbox/anbox-modules but when I got to

I posted a github repo a while back that's really just a rough scratchpad on my work with LXD, but you can see in this folder https://github.com/spacemule/LXDesktop/tree/main/Inspiration I have some examples of quick and dirty ways to spin up an Xserver. Also see the wonderful blog https://blog.simos.info/ He focuses mainly on LXD, but plenty of the tips are applicable to containerization in general. There's also a project, I forget the name and I don't have time to search right now. Maybe dockerx11 or something similar that is a set of scripts for exactly this kind of isolation. It should work just fine with podman.

I have a somewhat viable starting point to a solution to your problem: https://github.com/spacemule/LXDesktop