1.26.0¶

These release notes cover new features and changes in Anbox Cloud 1.26.0.

Anbox Cloud 1.26.0 is a minor release. To understand minor and patch releases, see Release notes.

Please see Component versions for a list of updated components.

Requirements¶

See the Requirements for details on general and deployment specific requirements to run Anbox Cloud.

You can now deploy Anbox Cloud using a reference Terraform plan in non-production environments. See Deploy with Terraform for detailed instructions. It is worth noting that this is an alpha release of the Terraform plan and that it is not meant for production environments.
To allow open source charms better integrate with our charms, we no longer block the installation of snaps within the charms if your Ubuntu Pro token in not attached. The deployment will proceed with a warning instead of failing. However, remember that without attaching an Ubuntu Pro token, you won’t be able to access images when the deployment is complete.
The Anbox Cloud charms now have support for Ubuntu 24.04 (Noble Numbat).
For the appliance deployment, service restarts now ask for your confirmation, unless you are using non-interactive mode. If you are using non-interactive mode, use the --no-restart flag to disable automatic restart of AMS and other required services.
Appliance initialization now gives clearer guidance on acceptable block devices.
If you use Juju 3.0 or later for your deployment, confidential data like private keys, API tokens, credentials managed by a charm, credentials passed between different charms via Juju relations is securely managed using Juju secrets.

You can now specify your GPU type when launching an instance by using the --gpu-type flag (Possible values:amd, intel, nvidia).
Default version for NVIDIA driver is 570.
AMS can now automatically determine if the instance is based on an application or an image. So you don’t have to use the --raw flag every time you launch an instance based on an image. Using amc launch <image_name> should launch the corresponding instance automatically.

The Anbox log level can be changed at runtime using the Anbox HTTP API. This is helpful in situations when you want to avoid a restart of the Anbox runtime.

We have the following enhancements to the Anbox Cloud dashboard:

Overhaul of the registry page
Customization of instance resources including CPU, GPU, memory
Authentication using Keycloak and Hydra. See Set up a custom identity provider for setup instructions.
Ability to revoke of a session share via ADB and also extend the validity of a share.
Notifications via websockets providing a reliable way to notify about asynchronous operations.

VM images now use hardware enablement kernels.
With this release, Android 15 (AOSP and AAOS) images are available.
Unused packages including netcat-openbsd, xxd, cron are removed from Android images.

We have upgraded to use the WebRTC revision 7049.
You can now explicitly disable certain video codecs (AV1, H264, VP8) even if they are supported by the client. Use the video.disabled_codecs option in the WebRTC streamer configuration file.

Android security updates for May 2025 (see Android Security Bulletin - May 2025).
The Android WebView has been updated to 136.0.7103.60.

The AMS node controller charm is deprecated in this release. See Deprecation notices for information about end of support.

The following issues exist in the 1.26.0 release and we are working to fix them for the 1.26.1 patch release:

A program was killed: context canceled error occurs during appliance initialization even though all services are active. (LP 2110321).
Security patch level for AOSP 15 and AAOS 15 remains unchanged at 2025-05-05 despite applying the latest security patches.(LP 2110323).
Unable to stream an instance after deploying the regular Anbox Cloud using Juju(LP 2110194). This issues exists since the 1.25.0 release. Run the following command to work around this issue:
```
juju ssh anbox-cloud-dashboard/0 -- "sudo sed -i '/^ASG_API_SERVER_CERTIFICATE: /d' /var/snap/anbox-cloud-dashboard/common/service/config.yaml"
juju ssh anbox-cloud-dashboard/0 -- "sudo snap restart anbox-cloud-dashbaord"
```
Once you relaunch the session, streaming will work properly.

Note

With the above workaround, HTTPS requests made by the dashboard will no longer verify SSL certificates, increasing the risk that data can be intercepted or altered. Hence only use only it in trusted environments. The proper fix will be included in the 1.26.1 release.

The Anbox Cloud 1.26.0 release includes fixes from the respective upstreams and components for the following CVEs:

LP 2107357 The image size for a new image version is displayed incorrectly.
LP 2109318 A segmentation fault was discovered in anbox-connect when trying to connect anbox instance.
LP 2106422 anbox-fs randomly fails at startup on instances.
LP 2101030 Telegraf unable to handle anbox_webrtc_frame_renderer_pending_buffers.
LP 2106106 Feature flags that have a . character in the name are not allowed in the dashboard.
LP 2109582 When removing a node, the hook fails because of a certificate not found error. When Juju reruns the hook, no issues occur.
LP 2106447 Private bug
LP 2108221 Private bug

See How to upgrade Anbox Cloud for instructions on how to update your Anbox Cloud deployment to the 1.26.0 release.