ISSUE
Instances launched from the following images in the 1.30.0 release end up in an error state:
resolute:android16-cf:amd64resolute:android16-cf:arm64resolute:aaos16-cf:amd64resolute:aaos16-cf:arm64
Inspecting the system log via amc logs reveals entries like these:
2026-06-29T05:09:38Z anbox-runtime.daemon[2110]: I20260629 05:09:38.243891 2110 gl_api.cpp:124] Loading EGL API from /snap/anbox-runtime/439/gpu-2404/usr/lib/x86_64-linux-gnu/libEGL.so.1
2026-06-29T05:09:38Z anbox-runtime.daemon[2110]: E20260629 05:09:38.243906 2110 platform.cpp:231] Failed to initialize GL API
2026-06-29T05:09:38Z anbox-runtime.daemon[2110]: Error: Platform initialization failed
2026-06-29T05:09:38Z systemd[1]: snap.anbox-runtime.daemon.service: Main process exited, code=exited, status=1/FAILURE
2026-06-29T05:09:38Z systemd[1]: snap.anbox-runtime.daemon.service: Failed with result 'exit-code'.
This was caused by a recent update to the mesa-2404 snap from the latest/stable channel. Its internal library layout changed slightly, and the anbox-runtime snap from the 1.30 channel does not yet account for that change. The mesa-2404 snap has been reverted to the working version 25.0.7-snap211.
WORKAROUND
To get instances launching properly again, we suggest the following steps:
-
Launch the instance with
--devmodeto enable developer mode for the instance:amc launch resolute:android16-cf:amd64 --enable-streaming --devmode -
Refresh the
mesa-2404snap from thelatest/stablechannel:amc exec <instance_id> -- snap refresh mesa-2404 --channel=latest/stable -
Hold the
mesa-2404snap to prevent automatic refreshes:amc exec <instance_id> -- snap refresh --hold=forever mesa-2404 -
Restart the
anbox-runtimesnap:amc exec <instance_id> -- snap restart anbox-runtime
We’re going to get this issue sorted in the next patch, so the above steps would no longer be needed from the 1.30.1 release.