[pinephone/phosh] anbox-image not installed automatically with anbox, and anbox package prints misleading notice to manually get anbox.img

Update: So, the problem was I got anbox.img manually because I came through apk add anbox and that told me to do so. Since that isn't actually what one is supposed to do on postmarketOS, I think the actual problem is that notice shouldn't be there and anbox-image should be automatically installed as a dependency.

Old, confused ticket before this cause was figured this out:

---

When I launch the graphical Anbox application I just see the loading screen for a while, then it just closes again with nothing useful ever shown. Afterwards I find these messages in /var/log/messages:

2020-06-18T05:09:48.262972+02:00 phone : Application manager service is not running yet
2020-06-18T05:10:05.832102+02:00 phone NetworkManager[2554]: <info>  [1592449805.8320] manager: (vethbDK9zC): new Veth device (/org/freedesktop/NetworkManager/Devices/9)
2020-06-18T05:10:05.856210+02:00 phone NetworkManager[2554]: <info>  [1592449805.8561] device (vethbDK9zC): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external')
2020-06-18T05:10:05.862569+02:00 phone NetworkManager[2554]: <info>  [1592449805.8625] device (vethbDK9zC): carrier: link connected
2020-06-18T05:10:05.887750+02:00 phone NetworkManager[2554]: <info>  [1592449805.8876] settings: (vethbDK9zC): created default wired connection 'Wired connection 1'
2020-06-18T05:10:05.895610+02:00 phone NetworkManager[2554]: <info>  [1592449805.8955] device (anbox0): carrier: link connected
2020-06-18T05:10:05.930683+02:00 phone NetworkManager[2554]: <info>  [1592449805.9306] device (vethbDK9zC): state change: unavailable -> disconnected (reason 'connection-assumed', sys-iface-state: 'external')
2020-06-18T05:10:05.936825+02:00 phone NetworkManager[2554]: <info>  [1592449805.9367] device (vethbDK9zC): Activation: starting connection 'vethbDK9zC' (0425aebf-f7cb-40a6-8c2d-5b76e9e872fa)
2020-06-18T05:10:05.938034+02:00 phone NetworkManager[2554]: <info>  [1592449805.9379] device (vethbDK9zC): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'external')
2020-06-18T05:10:05.942981+02:00 phone NetworkManager[2554]: <info>  [1592449805.9429] device (vethbDK9zC): state change: prepare -> config (reason 'none', sys-iface-state: 'external')
2020-06-18T05:10:05.950537+02:00 phone NetworkManager[2554]: <info>  [1592449805.9504] device (vethbDK9zC): state change: config -> ip-config (reason 'none', sys-iface-state: 'external')
2020-06-18T05:10:05.955460+02:00 phone NetworkManager[2554]: <info>  [1592449805.9554] device (anbox0): bridge port vethbDK9zC was attached
2020-06-18T05:10:05.955685+02:00 phone NetworkManager[2554]: <info>  [1592449805.9556] device (vethbDK9zC): Activation: connection 'vethbDK9zC' enslaved, continuing activation
2020-06-18T05:10:05.957139+02:00 phone NetworkManager[2554]: <info>  [1592449805.9570] device (vethbDK9zC): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'external')
2020-06-18T05:10:05.974947+02:00 phone dbus-daemon[2451]: [system] Activating service name='org.freedesktop.nm_dispatcher' requested by ':1.1' (uid=0 pid=2554 comm="/usr/sbin/NetworkManager -n ") (using servicehelper)
2020-06-18T05:10:06.008695+02:00 phone NetworkManager[2554]: <info>  [1592449806.0086] device (vethbDK9zC): state change: ip-check -> unmanaged (reason 'unmanaged', sys-iface-state: 'removed')
2020-06-18T05:10:06.015491+02:00 phone NetworkManager[2554]: <info>  [1592449806.0154] device (vethbDK9zC): released from master device anbox0
2020-06-18T05:10:06.074872+02:00 phone dbus-daemon[2451]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
2020-06-18T05:10:06.369296+02:00 phone : Failed to start container: Failed to start container: Failed to start container
2020-06-18T05:10:06.369386+02:00 phone : Lost connection to container manager, terminating.
2020-06-18T05:10:06.891404+02:00 phone : Container is not running
2020-06-18T05:10:06.891671+02:00 phone : Lost connection to container manager, terminating.

The service was running before and is still running after, so that part should be fine:

$ sudo rc-service --list | grep anbox
[sudo] password for user: 
anbox-container-manager
$ sudo rc-service anbox-container-manager start
 * WARNING: anbox-container-manager has already been started

I also do have the image in its place:

$ stat /usr/share/anbox/android.img 
  File: /usr/share/anbox/android.img
  Size: 325902336 	Blocks: 636528     IO Block: 4096   regular file
Device: fe00h/65024d	Inode: 262287      Links: 1
Access: (0644/-rw-r--r--)  Uid: (    0/    root)   Gid: (    0/    root)
Access: 2020-06-18 05:03:20.000000000
Modify: 2020-06-11 18:39:12.000000000
Change: 2020-06-11 18:39:12.000000000

Is this a known issue of sorts?