Anbox Cloud 1.25.0 has been released

Anbox Cloud
1

1.25.0

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

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

Important:
The 1.25.0 release contains new versions of the Anbox Cloud snaps and images. There are no charms released for 1.25.0, they are instead planned to be released in 1.25.1.

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.

New features & improvements

Anbox Cloud Dashboard

  • The dashboard now includes an onboarding tour for new users. Click Get Started on the navigation to take the tour.
  • A new Images page is included in the Anbox Cloud dashboard so that you can directly add an image or work with the existing images.
  • Enhancements to the following forms and pages:
    • Create Application
    • Edit Application
    • Create Instance
    • Profile
    • Application details

AMS

  • When querying image related information, you can now see the image variant without waiting for the full image to be downloaded.
  • The GPU type is included in the AMS node API object, to provide better visibility into hardware specifications.

Stream Gateway

  • An administrator can revoke a pre-signed ADB connection URL before it expires, to prevent malicious actions using the command:

    anbox-stream-gateway share delete <share_id>

See {ref}howto-access-instance for more information.

  • You can now update the expiration date, description and the timeout values of a shared session using the command:

      anbox-stream-gateway share update <share_id> --expiry=30m --description=new_description

  • The Stream Gateway now uses the latest Dqlite LTS version.

  • Anbox Cloud uses WebRTC 6778.

Monitoring

  • A new /1.0/metrics endpoint is added to support collecting metrics from the Anbox runtime.

Other

Removed functionality

  • Starting with the 1.25.0 release, the appliance snap with epoch=0 is removed and unsupported. This epoch will no longer receive updates.
    To start using the new appliance snap with epoch=1, a fresh install of the appliance snap is required.

Deprecations

The following deprecations are announced as part of the 1.25.0 release. See {ref}ref-deprecation-notes for more information on when the support for these items will be dropped:

  • The support for LXD 5.0 snap is deprecated.
  • The support for kernel 6.8 and earlier is deprecated.

CVEs

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

CVE Affected Components
CVE-2024-49721 Android 12,13
CVE-2023-40133 Android 12,13
CVE-2023-40134 Android 12,13
CVE-2023-40135 Android 12,13
CVE-2023-40136 Android 12,13
CVE-2023-40137 Android 12,13
CVE-2023-40138 Android 12,13
CVE-2023-40139 Android 12,13
CVE-2024-49743 Android 12,13,14
CVE-2024-49746 Android 12,13,14
CVE-2023-40122 Android 12,13,14
CVE-2024-49729 Android 12,13,14
CVE-2024-0037 Android 12,13,14
CVE-2025-0100 Android 12,13,14
CVE-2024-49741 Android 12,13,14
CVE-2025-0094 Android 12,13,14
CVE-2025-0091 Android 12,13,14
CVE-2025-0095 Android 14
CVE-2024-53103 Ubuntu 22.04 Linux kernel

Bug fixes

  • LP 2095559 When stopping an instance with GPU slots and starting it later on, the instance fails to start. This issue was caused by multiple GPUs attached to the LXD container interfering with how the Anbox Cloud scripts detect the NVIDIA driver version.
  • LP 2095551 When creating an application, the hooks.timeout property is auto-populated to have an empty value and this causes the operation to fail.
  • LP 2095179 Unable to log in to the Anbox Cloud dashboard after updating the appliance’s network address.
  • LP 2089261 After restarting the host machine running Anbox Cloud, the instances that have a running status need to be restarted. This is due to an issue where the status of the instance in LXD is not in sync with the status in AMS.
  • LP 2093887 Launching an instance from a jammy:android12:amd64 VM image floods the journal logs with Operation not permitted errors.
  • LP 2092193 Some Anbox system services take a longer time than usual to get started and show high CPU usage.
  • LP 2091921 The dashboard generates an anbox-connect command on demand, but the connection URL that is displayed as part of the output is not enclosed within quotes, causing issues when copying and running the command in a fish shell.
  • LP 2094279 Instance deletion does not happen in the background. When an instance is deleted and you are accessing a stream of a different instance, the streaming web page navigates back to the Instance page to confirm the deletion of the other instance.
  • LP 2086853 On all Android versions, irrespective of whether the instance is a container or a VM, taking pictures or videos from the default camera application results in only black and white pictures/videos with software rendering. This issue does not happen with a GPU.
  • LP 2095568 The API swagger documentation states that /1.0/applications/{id}/manifest GET states that AMS returns JSON when AMS is actually returning an octet-stream.
  • LP 2096666 When using the registration URL for the dashboard more than once, the following error occurs: Error adding user to database.
  • LP 2096982 The name for the field that is used to set an expiration timestamp for a session share is inconsistent across the different API requests and responses.
    To avoid confusion, the field naming should be consistent across all requests and responses.
  • LP 2071806 Private bug
  • LP 2091609 Private bug
  • LP 2096628 Private bug
  • GitHub Issue 251 We have updated the prometheus metrics documentation to reflect accurate information.

Upgrade instructions

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

1 Like