Jammy release of Anbox

[pccobbler]

The webpage at https://ppa.launchpadcontent.net/morphis/anbox-support/ubuntu/dists/ shows that there is no Jammy release, with all content being from 2018. Anbox does not work on Jammy because apt fails. Is a Jammy release of Anbox forthcoming?

~$ snap install --devmode --beta anbox
anbox (beta) 4-56c25f1 from Simon Fels (morphis) installed

~$ sudo add-apt-repository ppa:morphis/anbox-support
[sudo] password for userr:
Repository: 'deb https://ppa.launchpadcontent.net/mor...upport/ubuntu/ jammy main'
More info: https://launchpad.net/~morphis/+arch.../anbox-support
Adding repository.
Press [ENTER] to continue or Ctrl-c to cancel.
Adding deb entry to /etc/apt/sources.list.d/morphis-ubuntu-anbox-support-jammy.list
Adding disabled deb-src entry to /etc/apt/sources.list.d/morphis-ubuntu-anbox-support-jammy.list
Adding key to /etc/apt/trusted.gpg.d/morphis-ubuntu-anbox-support.gpg with fingerprint CFD4CCDE77B82D4FA3B113E521C6044A875B67B7
Get:1 http://us.archive.ubuntu.com/ubuntu jammy InRelease [270 kB]
Hit:2 http://security.ubuntu.com/ubuntu jammy-security InRelease
Ign:3 https://repo.vivaldi.com/stable/deb stable InRelease
Hit:4 https://repo.vivaldi.com/stable/deb stable Release
Hit:5 http://us.archive.ubuntu.com/ubuntu jammy-updates InRelease
Hit:6 http://us.archive.ubuntu.com/ubuntu jammy-backports InRelease
Get:7 http://us.archive.ubuntu.com/ubuntu jammy/universe amd64 Packages [13.6 MB]
Ign:9 https://ppa.launchpadcontent.net/mor...support/ubuntu jammy InRelease
Err:10 https://ppa.launchpadcontent.net/mor...support/ubuntu jammy Release
404 Not Found [IP: 91.189.95.85 443]
Get:11 http://us.archive.ubuntu.com/ubuntu jammy/universe i386 Packages [7,491 kB]
Get:12 http://us.archive.ubuntu.com/ubuntu jammy/universe Translation-en [5,651 kB]
Get:13 http://us.archive.ubuntu.com/ubuntu jammy/universe amd64 c-n-f Metadata [286 kB]
Reading package lists... Done
E: The repository 'https://ppa.launchpadcontent.net/morphis/anbox-support/ubuntu jammy Release' does not have a Release file.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.

~$ sudo apt update
Hit:1 http://us.archive.ubuntu.com/ubuntu jammy InRelease
Hit:2 http://us.archive.ubuntu.com/ubuntu jammy-updates InRelease
Hit:3 http://us.archive.ubuntu.com/ubuntu jammy-backports InRelease
Hit:4 http://security.ubuntu.com/ubuntu jammy-security InRelease
Ign:5 https://repo.vivaldi.com/stable/deb stable InRelease
Hit:6 https://repo.vivaldi.com/stable/deb stable Release
Ign:7 https://ppa.launchpadcontent.net/mor...support/ubuntu jammy InRelease
Err:9 https://ppa.launchpadcontent.net/mor...support/ubuntu jammy Release
404 Not Found [IP: 91.189.95.85 443]
Reading package lists... Done
E: The repository 'https://ppa.launchpadcontent.net/morphis/anbox-support/ubuntu jammy Release' does not have a Release file.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.

~$ sudo apt install linux-headers-generic anbox-modules-dkms
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
E: Unable to locate package anbox-modules-dkms

~$ sudo modprobe ashmem_linux
~$ sudo modprobe binder_linux

~$ ls -1 /dev/{ashmem,binder}
ls: cannot access '/dev/binder': No such file or directory
/dev/ashmem

[aroesler-privat]

Hi!

I am trying to run anbox on Ubuntu 22.04 as well, but failed at another point. Finally it is up and running now, but maybe slower as it should due to software rendering.

I think the issue you pointed out can be solved like described in https://bugs.launchpad.net/ubuntu/+source/anbox/+bug/1884810/comments/8 :

sudo modprobe ashmem_linux
sudo modprobe binder_linux
sudo mkdir /dev/binderfs
sudo mount -t binder binder /dev/binderfs

@pccobbler , does this solve your problem?

I could get anbox starting by following https://gitanswer.com/anbox-xubuntu-20-04-anbox-apps-do-not-open-c-757978637#747681062 :

sudo snap set anbox software-rendering.enable=true
sudo snap restart anbox.container-manager

And ran in parallel (two terminals):

$ anbox session-manager
$ anbox.appmgr

Nevertheless, right now I (still) get those errors:

$ anbox session-manager
libGL error: pci id for fd 11: 8086:9b41, driver (null)
libGL error: No driver found
libGL error: failed to load driver: (null)
libGL error: pci id for fd 11: 8086:9b41, driver (null)
libGL error: unable to load driver: iris_dri.so
libGL error: driver pointer missing
libGL error: failed to load driver: iris

[pccobbler]

@aroesler-privat

I will try your suggestions on the original system later (it's on a USB flash drive). But using a different USB flash drive, I installed Bionic Beaver and was able to get Anbox to install and start.

[videni]

However got this error

anbox session-manager
anbox.appmgr
/snap/anbox/186/usr/bin/anbox: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.25' not found (required by libsystemd.so.0)
/snap/anbox/186/usr/bin/anbox: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.27' not found (required by libsystemd.so.0)
/snap/anbox/186/usr/bin/anbox: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.25' not found (required by libsystemd.so.0)
/snap/anbox/186/usr/bin/anbox: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.27' not found (required by libsystemd.so.0)

[Fuseteam]

That PPA hasn't been needed since 19.04 where did you dig that up from?
The apt version of anbox comes directly from debian and is likely an older release than the snap version

Sadly it sounds like the real issue is related to glib somehow 🤔

[jeniljain18]

It shows this error to me

[jeniljain18]

It shows this error to me

And even if it gets install it doesn't take any inputs....

[Fuseteam]

@jeniljain18 the PPA hasn't been needed for 3 years now, where did you get that ppa from?

[pengxu-github]

@jeniljain18 the PPA hasn't been needed for 3 years now, where did you get that ppa from?

is there any documents that list steps of run manually compiled anbox？I run container-manager success，but session manager failed with [ 2022-05-11 09:53:11] [session_manager.cpp:149@operator()] Failed to start as either binder or ashmem kernel drivers are not loaded, aftersudo mkdir /dev/binderfsandsudo mount -t binder binder /dev/binderfs`, also failed.

anbox session-manager
[ 2022-05-12 07:57:35] [client.cpp:48@start] Failed to start container: Failed to start container: Failed to start container
[ 2022-05-12 07:57:35] [session_manager.cpp:164@operator()] Lost connection to container manager, terminating.
[ 2022-05-12 07:57:35] [daemon.cpp:61@Run] Container is not running
terminate called after throwing an instance of 'boost::wrapexcept<boost::log::v2_mt_posix::system_error>'
  what():  Failed to set TLS value: Invalid argument
Stack trace (most recent call last) in thread 2884831:
#16   Object "[0xffffffffffffffff]", at 0xffffffffffffffff, in 
#15   Object "/lib/x86_64-linux-gnu/libc.so.6", at 0x7fac7984b162, in clone
#14   Object "/lib/x86_64-linux-gnu/libpthread.so.0", at 0x7fac79bbe608, in 
#13   Object "/usr/lib/x86_64-linux-gnu/libstdc++.so.6", at 0x7fac79a0fde3, in 
#12   Object "/mnt/nvme/code/freemeos-code/harmony/container-things/anbox/install_dir/bin/anbox", at 0x562eb11da934, in 
#11   Object "/mnt/nvme/code/freemeos-code/harmony/container-things/anbox/install_dir/bin/anbox", at 0x562eb1200fac, in void anbox::Logger::Errorf<char const*>(boost::optional<anbox::Logger::Location> const&, std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&, char const*&&)
#10   Object "/mnt/nvme/code/freemeos-code/harmony/container-things/anbox/install_dir/bin/anbox", at 0x562eb1202d45, in 
#9    Object "/usr/lib/x86_64-linux-gnu/libboost_log.so.1.71.0", at 0x7fac7a02f91a, in boost::log::v2_mt_posix::sources::aux::get_severity_level()
#8    Object "/usr/lib/x86_64-linux-gnu/libboost_log.so.1.71.0", at 0x7fac7a05a239, in boost::log::v2_mt_posix::aux::thread_specific_base::set_content(void*) const
#7    Object "/usr/lib/x86_64-linux-gnu/libboost_log.so.1.71.0", at 0x7fac7a00ecdc, in 
#6    Object "/usr/lib/x86_64-linux-gnu/libboost_log.so.1.71.0", at 0x7fac7a00ffb2, in 
#5    Object "/usr/lib/x86_64-linux-gnu/libstdc++.so.6", at 0x7fac799e36a8, in __cxa_throw
#4    Object "/usr/lib/x86_64-linux-gnu/libstdc++.so.6", at 0x7fac799e33f6, in std::terminate()
#3    Object "/usr/lib/x86_64-linux-gnu/libstdc++.so.6", at 0x7fac799e338b, in 
#2    Object "/usr/lib/x86_64-linux-gnu/libstdc++.so.6", at 0x7fac799d7910, in 
#1    Object "/lib/x86_64-linux-gnu/libc.so.6", at 0x7fac7974e858, in abort
#0    Object "/lib/x86_64-linux-gnu/libc.so.6", at 0x7fac7976f03b, in gsignal
Aborted (Signal sent by tkill() 2884818 1000)
Aborted (core dumped)

[Fuseteam]

@pengxu-github are you manually compiling anbox?

[pengxu-github]

yes，i want do some debug of anbox, but can not run the manually compiled bins.

[Fuseteam]

@pengxu-github then i don't think this is appropiate place for this discussion, you might get better answers on telegram, the group should be linked on anbox.io

[pengxu-github]

ok，thanks a lot

[JarEXE]

@jeniljain18 the PPA hasn't been needed for 3 years now, where did you get that ppa from?

Anbox official documentation states, that before installing the snap, one should Install necessary kernel modules, which then leads to the deceased PPA.

https://docs.anbox.io/userguide/install.html

[musichemist]

@Fuseteam Here is how someone gets the ppa

Go to anbox.io
Click "Install Anbox"
Get taken to https://docs.anbox.io/userguide/install.html, which directs you to add the ppa and kernel modules

Which I did - Anbox didn't work
Removed Anbox

Now cannot remove the kernel modules!

sudo ppa-purge ppa:morphis/anbox-support
Updating packages lists
E: The repository 'https://ppa.launchpadcontent.net/morphis/anbox-support/ubuntu jammy Release' does not have a Release file.
Warning: apt-get update failed for some reason

I've spent half a day trying to remove these with no luck.

[Fuseteam]

@jeniljain18 the PPA hasn't been needed for 3 years now, where did you get that ppa from?

Anbox official documentation states, that before installing the snap, one should Install necessary kernel modules, which then leads to the deceased PPA.

https://docs.anbox.io/userguide/install.html

Take a closer look at https://docs.anbox.io/userguide/install_kernel_modules.html and i quote

Starting with Ubuntu 19.04 binder and ashmem are now build with the standard Ubuntu kernel (>= 5.0) and you don’t have to install the modules from the PPA anymore.

[Fuseteam]

@Fuseteam Here is how someone gets the ppa

Go to anbox.io
Click "Install Anbox"
Get taken to https://docs.anbox.io/userguide/install.html, which directs you to add the ppa and kernel modules

So you're telling me people just read past the big blue box? Are you serious?

Also i doubt you actually installed the modules as that repo has no build of the modules past ubuntu 19.04, you likely just have to remove the modules entry in /etc/apt/sources if i remember my paths right

[musichemist]

If by "people" you mean me - I never saw that blue box. This link takes you straight to https://docs.anbox.io/userguide/install.html and there is no indication that this info is out of date. How hard would it be to edit or remove this page? It's taking novices (again, me) down the wrong path.

[musichemist]

Also, I only found this page after the fact. I followed instructions in the July 2022 issue of this magazine: https://unredactedmagazine.com/download.html

And I'm not stupid, but I'm new to Linux. I can't figure out how to remove the kernel modules. The ppa commands don't work since there's no jammy Release and the files cannot be deleted from my user account because I don't have permission and cannot change it. Maybe I can boot into safe mode (or whatever Ubuntu calls that) and get root access but that's another half day of googling and learning by trial and error that I don't have right now.

[Fuseteam]

@musichemist sure it takes you to https://docs.anbox.io/userguide/install.html that is fine, but the first step should take you to install kernel modules which is where that big blue box is from.

And no by 'people' i mean people in general, i see this issue a lot, and i mean a lot

But yes you can change it, you need to remove the ppa line from your config.
Try this command to find where it comes from:

grep -r anbox /etc/apt/

It should showl the exact file you need
Then run

sudo nano /etc/apt/sources.list

Remove the line mentioning anbox, save and close with ctrl+x, and run sudo apt update

P.s. The info isn't out of date per se, it's simply not relavant past ubuntu 19.04. It is still relevant for ubuntu 18.04, which is very much still supported

P.p.s.

Also, I only found this page after the fact. I followed instructions in the July 2022 issue of this magazine: https://unredactedmagazine.com/download.html

That i can believe and the reason i originally asked, there are a bunch of outdated guides outside of docs.anbox.io that need to be updated.

Granted 22.04 may very well be the last version anbox will work on

[dylanosaur]

Unfortunately this seems to still not work out of the box. It seems the drivers required for Anbox do not ship with Ubuntu 22 by default. The PPA referenced above is used to install those drivers, but it does not have a release for Jammy Jellyfish.

[Fuseteam]

the "drivers" used for this is shipped with the stock ubuntu 22.04 kernel you do not need the PPA