Anbox installation - Troubleshooting

markh4b

Update: Meanwhile I tried repartitioning the device with a method from here: The one that increases the partition size to 6gb (previous partition size was 2gb, checked that beforehand). Now the device still boots correctly and works normally, but adb shell connection gets stuck on updates/installations somewhere between 90% and 100%. Error message is usually that the device is out of memory.

arubislander

@markh4b I get the same results as you trying to install a snap inside a libertine container. I think it has something to do with it the fact that the exec command does not set up the same bindings as the libertine-launch command does.

Concerning the errors when installing from the 'repartitioned' filesystem, could you post the exact error message?

markh4b

@arubislander It was a really generic message, such as "not enough space left on device". I cannot remember exactly, and I can offer to reproduce it from the 12th of August onward. Currently the device is flashed with Android, instead of Ubuntu.

arubislander

@markh4b Ah, OK. That's an out-of-storage-space error. Either the extra 4 Gigs were still not enough or the filesystem was not expanded to make use of the extra space.

markh4b

@arubislander Probably the latter, because I hardly understand whether the commands are sufficient:

$ sudo -s
# dd if=/dev/null of=/userdata/ubuntu.img bs=1M seek=6000 count=0
# resize2fs -f /userdata/ubuntu.img
# reboot

My best guess is that it seeks 6000 blocks of size 1 megabyte each, and writes those to a file ubuntu.img, then resizes/expands the root partition with this new file and reboots?

arubislander

@markh4b
Yes, I don't understand the seek part myself. But my guess is that it just increases the size of whatever file was already there.
But the resize command should result in the filesystem using the newly created space.

doniks

@arubislander said in Anbox installation - Troubleshooting:

@markh4b I get the same results as you trying to install a snap inside a libertine container. I think it has something to do with it the fact that the exec command does not set up the same bindings as the libertine-launch command does.

Sounds plausible. Did you try with libertine-launch?

doniks

@markh4b said in Anbox installation - Troubleshooting:

@arubislander Probably the latter, because I hardly understand whether the commands are sufficient:

$ sudo -s
# dd if=/dev/null of=/userdata/ubuntu.img bs=1M seek=6000 count=0
# resize2fs -f /userdata/ubuntu.img
# reboot

My best guess is that it seeks 6000 blocks of size 1 megabyte each, and writes those to a file ubuntu.img, then resizes/expands the root partition with this new file and reboots?

I don't understand it either. I simply do resize2fs ubuntu.img 5G from TWRP. No dd needed. (And certainly no sudo !). At most it might want you to fsck -y, but resize2fs will tell you if it's needed

arubislander

@doniks said in Anbox installation - Troubleshooting:

Sounds plausible. Did you try with libertine-launch?

Yes, I did. It tells me it cannot find the snap command. Furhtermore: libertine-launch apt search snap | grep snap returns only

libsnappy1v5/now 1.1.3-2 armhf [installed,local]

I would have expected at least snapd to appear in that list.

doniks

@arubislander

Waaait a minute. First you said

@arubislander said in Anbox installation - Troubleshooting:

@markh4b I get the same results as you trying to install a snap inside a libertine container.

I understood that you were referring to @markh4b post where he describes a botched attempt of installing some packages via apt and running out of diskspace, however at the end he has snap installed nevertheless, but not working properly.

Now you say

Furhtermore: libertine-launch apt search snap | grep snap returns only
libsnappy1v5/now 1.1.3-2 armhf [installed,local]
I would have expected at least snapd to appear in that list.

Now I'm confused. Which way is it? Are you getting the same results as @markh4b or are you failing at a totally different step where snap is not even being offered to be installed from apt?

arubislander

@doniks said in Anbox installation - Troubleshooting:

Which way is it? Are you getting the same results as @markh4b or are you failing at a totally different step where snap is not even being offered to be installed from apt?

It is both. I can do libertine-container-manager install-package -p snapd and the package gets installed. It even shows that it is installed in the Libertine GUI under the Settings. And after that I get the same results as @markh4b did. But the snapd package does not show up in the list with libertine-launch apt search snap | grep snap.

The two things are probably totally unrelated. The reason snapd does not work in the container, I guess, is that since the libertine container is a chroot, it doesn't use systemd, and snapd depends on systemd to work properly. The reason the snapd package does not show up in a apt search snap I cannot begin to guess about.

doniks

Strange.

arubislander

@doniks
when I do: libertine-container-manager exec -c 'apt update && apt search snapd' I do get the snapd package listed. So, that mystery is also solved.

markh4b

Another update: Tried anbox on my desktop first, and there are lots of issues with the apps. So most likely I'll leave Android installed on the tablet directly.